# CVE-2026-34764: Electron has a use-after-free in offscreen shared texture release() callback > Electron apps using offscreen shared textures may suffer use-after-free, allowing attackers to cause crashes or execute code via memory corruption. - **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Apr 2026 - **Updated:** 7 Apr 2026 - **Also known as:** GHSA-8x5q-pvf5-64mp ## What is CVE-2026-34764? CVE-2026-34764 is a low-severity use after free vulnerability in Electronjs Electron, published on 6 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 33.0.0-alpha.1 to before 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5, apps that use offscreen rendering with GPU shared textures may be vulnerable to a use-after-free. Under certain conditions, the release() callback provided on a paint event texture can outlive its backing native state, and invoking it after that point dereferences freed memory in the main process, which may lead to a crash or memory corruption. Apps are only affected if they use offscreen rendering with webPreferences.offscreen: { useSharedTexture: true }. Apps that do not enable shared-texture offscreen rendering are not affected. To mitigate this issue, ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable. This vulnerability is fixed in 39.8.5, 40.8.5, 41.1.0, and 42.0.0-alpha.5. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2026-34764? 8 open source packages ship an affected version, including electron. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `electron` | npm | From 33.0.0-alpha.1 | 39.8.5 | | `electron` | npm | From 33.0.0-alpha.1 | 39.8.5 | | `electron` | npm | From 40.0.0-alpha.1 | 40.8.5 | | `electron` | npm | From 40.0.0-alpha.1 | 40.8.5 | | `electron` | npm | From 41.0.0-alpha.1 | 41.1.0 | | `electron` | npm | From 41.0.0-alpha.1 | 41.1.0 | | `electron` | npm | From 42.0.0-alpha.1 | 42.0.0-alpha.5 | | `electron` | npm | From 42.0.0-alpha.1 | 42.0.0-alpha.5 | Products: Electronjs Electron. ## How do I fix CVE-2026-34764? Upgrade electron to a fixed version for your release line: 39.8.5, 40.8.5, 41.1.0 or 42.0.0-alpha.5. ## Is CVE-2026-34764 being exploited? There is no known exploitation of CVE-2026-34764 in the wild and no public exploit code. ## Other vulnerabilities in Electronjs Electron - [CVE-2017-16151](https://insights.sbomify.com/CVE-2017-16151/): Chromium Remote Code Execution in electron (critical 9.8) - [CVE-2018-1000118](https://insights.sbomify.com/CVE-2018-1000118/): Electron protocol handler browser vulnerable to Command Injection (high 8.8) - [CVE-2026-34780](https://insights.sbomify.com/CVE-2026-34780/): Electron: Context Isolation bypass via contextBridge VideoFrame transfer (high 8.4) - [CVE-2026-102676](https://insights.sbomify.com/CVE-2026-102676/): Electron: can enable Node.js integration in Web Workers despite embedder restrictions (high 8.3) - [CVE-2026-102673](https://insights.sbomify.com/CVE-2026-102673/): Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-34764 and fix it if it is affected. What it is: CVE-2026-34764 is a low-severity use after free vulnerability in Electronjs Electron, published on 6 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-34764 in the wild and no public exploit code. Affected packages and fixed versions: - electron (npm): affected from 33.0.0-alpha.1; fixed in 39.8.5 - electron (npm): affected from 33.0.0-alpha.1; fixed in 39.8.5 - electron (npm): affected from 40.0.0-alpha.1; fixed in 40.8.5 - electron (npm): affected from 40.0.0-alpha.1; fixed in 40.8.5 - electron (npm): affected from 41.0.0-alpha.1; fixed in 41.1.0 - electron (npm): affected from 41.0.0-alpha.1; fixed in 41.1.0 - electron (npm): affected from 42.0.0-alpha.1; fixed in 42.0.0-alpha.5 - electron (npm): affected from 42.0.0-alpha.1; fixed in 42.0.0-alpha.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-34764/ (Markdown: https://insights.sbomify.com/CVE-2026-34764/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34764 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34764 - OSV: https://osv.dev/vulnerability/CVE-2026-34764 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-34764/ Summaries are generated and may contain mistakes; the official description above is the record.