Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-8x5q-pvf5-64mp

LOW

GHSA-8x5q-pvf5-64mp is a low-severity (CVSS 2.3) Use After Free vulnerability in electron. O3 Security confirms whether GHSA-8x5q-pvf5-64mp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-34764
Published
Apr 3, 2026
Updated
Apr 6, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

electronnpm
5.7Mdownloads / week

Description

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 [email protected]

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectron33.0.0-alpha.1&&< 39.8.539.8.5
📦npmelectron40.0.0-alpha.1&&< 40.8.540.8.5
📦npmelectron41.0.0-alpha.1&&< 41.1.041.1.0
📦npmelectron42.0.0-alpha.1&&< 42.0.0-alpha.542.0.0-alpha.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update electron to 39.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x5q-pvf5-64mp is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8x5q-pvf5-64mp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8x5q-pvf5-64mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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()`
O3 Security · Impact-Aware SCA

Is GHSA-8x5q-pvf5-64mp in your dependencies?

O3 detects GHSA-8x5q-pvf5-64mp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.