NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
LOW severity

CVE-2026-70598 — electron

LOWFix: electron/electron@2c24640

CVE-2026-70598 is a low-severity (CVSS 3.9) Out-of-bounds Read vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: Off-screen rendering trusts GPU-supplied geometry over shared-memory size

Also known asGHSA-pfmc-3mgc-p6fp
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-70598.

EPSS Exploitation Probability

via FIRST.org ↗
0.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk
0.00%0.21%0.42%0.64%0.1%0.1%0.1%0.1%Sep 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
electronnpm
12.2Mdownloads / week

Description

Impact

In offscreen rendering mode, frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing paint event images, disclosing memory or crashing the app.

Apps are only affected if they use offscreen rendering (webPreferences.offscreen) and an attacker has separately gained code execution in the GPU process. Apps that do not use offscreen rendering are not affected.

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

  • 42.0.0-beta.3
  • 41.2.1
  • 40.9.0
  • 39.8.10

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectronall versions39.8.10npm install electron@39.8.10
📦npmelectron≥ 40.0.0-alpha.1&&< 40.9.040.9.0npm install electron@40.9.0
📦npmelectron≥ 41.0.0-alpha.1&&< 41.2.141.2.1npm install electron@41.2.1
📦npmelectron≥ 42.0.0-alpha.1&&< 42.0.0-beta.342.0.0-beta.3npm install electron@42.0.0-beta.3

Affected Products

1 product · 11 configurations
Application
electronelectronjs
≥ 41.0.0 && < 41.2.1
1 version
42.0.0

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update electron to 39.8.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-70598 is resolved across your whole dependency graph.

  3. Workarounds

    Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

### Impact In offscreen rendering mode, frame data received from the GPU process was not fully validated by the main process. A compromised GPU process could cause the main process to read out-of-bounds memory while producing `paint` event images, disclosing memory or crashing the app. Apps are only affected if they use offscreen rendering (`webPreferences.offscreen`) and an attacker has separately gained code execution in the GPU process. Apps that do not use offscreen rendering are not affected. ### Workarounds There are no app side workarounds, you must update to a patched version of Elec
O3 Security · Impact-Aware SCA

Is CVE-2026-70598 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2026-70598: electron — Fixed in 39.8.10