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

CVE-2026-70604 — electron

HIGH

CVE-2026-70604 is a high-severity (CVSS 7.4) CWE-942 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin reads

Also known asGHSA-v3j7-r9gq-3gjw
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 3, 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-70604.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.28%0.57%0.85%0.3%0.4%0.4%0.4%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

A custom scheme registered with supportFetchAPI: true but without corsEnabled: true was not subject to CORS enforcement. A page loaded from a remote origin could therefore fetch() or XMLHttpRequest that scheme cross-origin and read the full response body, rather than the read being blocked.

Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.

Workarounds

Set corsEnabled: true on schemes that must enforce CORS, and validate the request Origin in your protocol handler before returning sensitive data.

Fixed Versions

  • 42.0.0
  • 41.4.0
  • 40.9.3
  • 39.8.10

For more information

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

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmelectron≥ 42.0.0-alpha.1&&< 42.0.042.0.0npm install electron@42.0.0
📦npmelectron≥ 41.0.0-alpha.1&&< 41.4.041.4.0npm install electron@41.4.0
📦npmelectron≥ 40.0.0-alpha.1&&< 40.9.340.9.3npm install electron@40.9.3
📦npmelectronall versions39.8.10npm install electron@39.8.10

Affected Products

1 product · 17 configurations
Application
electronelectronjs
≥ 41.0.0 && < 41.4.0
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 42.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-70604 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.

Frequently Asked Questions

### Impact A custom scheme registered with `supportFetchAPI: true` but without `corsEnabled: true` was not subject to CORS enforcement. A page loaded from a remote origin could therefore `fetch()` or `XMLHttpRequest` that scheme cross-origin and read the full response body, rather than the read being blocked. Apps that serve sensitive data from such a scheme and load remote or untrusted content in a renderer are affected. Apps that set `corsEnabled: true`, or that do not load untrusted content, are not affected. ### Workarounds Set `corsEnabled: true` on schemes that must enforce CORS, and v
O3 Security · Impact-Aware SCA

Is CVE-2026-70604 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2026-70604: electron — Fixed in 42.0.0