cve.bz

CVE-2026-70604 electronjs electron

7.4 highEPSS 0.4%Fix available

High (7.4) in electronjs electron. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in electron 39.8.10, 40.9.3, 41.4.0.

On this page
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 40.9.3, 41.4.0, and 42.0.0, 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. This issue is fixed in versions 39.8.10, 40.9.3, 41.4.0, and 42.0.0.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-70604 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70604?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70604?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-70604 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
electronjs:electronbefore 39.8.10
electronjs:electronfrom 40.0.0 before 40.9.3
electronjs:electronfrom 41.0.0 before 41.4.0
electronjs:electron42.0.0:alpha1
electronjs:electron42.0.0:alpha2
electronjs:electron42.0.0:alpha3
electronjs:electron42.0.0:alpha4
electronjs:electron42.0.0:alpha5
electronjs:electron42.0.0:alpha6
electronjs:electron42.0.0:beta1
electronjs:electron42.0.0:beta2
electronjs:electron42.0.0:beta3
electronjs:electron42.0.0:beta4
electronjs:electron42.0.0:beta5
electronjs:electron42.0.0:beta6
electronjs:electron42.0.0:beta7
electronjs:electron42.0.0:beta8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v3j7-r9gq-3gjwnpmelectron>=42.0.0-alpha.1 <42.0.042.0.0
GHSA-v3j7-r9gq-3gjwnpmelectron>=41.0.0-alpha.1 <41.4.041.4.0
GHSA-v3j7-r9gq-3gjwnpmelectron>=40.0.0-alpha.1 <40.9.340.9.3
GHSA-v3j7-r9gq-3gjwnpmelectron<39.8.1039.8.10

References

Check your stackJSON