Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

Electron: Use-after-free in offscreen shared texture release() callback

CVE-2026-34764GHSA-8x5q-pvf5-64mp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 42.0.0-alpha.5, 41.1.0, 40.8.5, 39.8.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    >= 33.0.0-alpha.1, < 39.8.5>= 40.0.0-alpha.1, < 40.8.5>= 41.0.0-alpha.1, < 41.1.0>= 42.0.0-alpha.1, < 42.0.0-alpha.5
    Fixed in
    39.8.5, 42.0.0-alpha.5, 40.8.5, 41.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.3 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2026-34764: 0.10% estimated exploitation activity in the next 30 days; percentile 0.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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. Workarounds Ensure texture.release() is called promptly after the texture has been consumed, before the texture object becomes unreachable. Fixed Versions 42.0.0-alpha.5 41.1.0 40.8.5 39.8.5 For more information If there are any questions or comments about this advisory, send an email to security@electronjs.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8x5q-pvf5-64mp

  2. Revision 1 · created ·

    Published from osv record GHSA-8x5q-pvf5-64mp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34764

Advisory: Electron: Use-after-free in offscreen shared texture release() callback
IDs: CVE-2026-34764, GHSA-8x5q-pvf5-64mp
Record: https://patchnext.com/advisories/cve-2026-34764 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 42.0.0-alpha.5, 41.1.0, 40.8.5, 39.8.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected >= 33.0.0-alpha.1, < 39.8.5; >= 40.0.0-alpha.1, < 40.8.5; >= 41.0.0-alpha.1, < 41.1.0; >= 42.0.0-alpha.1, < 42.0.0-alpha.5; fixed in 39.8.5, 42.0.0-alpha.5, 40.8.5, 41.1.0

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8x5q-pvf5-64mp (OSV record GHSA-8x5q-pvf5-64mp lists affected ranges: npm electron >=33.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-alpha.5 (fixed))
- Verified: https://github.com/advisories/GHSA-8x5q-pvf5-64mp (GitHub-reviewed advisory GHSA-8x5q-pvf5-64mp lists affected ranges: npm electron >=33.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-alpha.5)

Commands are suggestions: review each one before running it.

Loading voting…