cve.bz

CVE-2026-70606 electronjs electron: Exposure of Resource to Wrong Sphere

5.9 mediumEPSS 0.3%Fix available

Medium (5.9) in electronjs electron. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in electron 40.10.6, 41.9.1, 42.5.1.

On this page
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 40.10.6, 41.9.1, 42.5.1, and 43.0.0, when a custom protocol handler returned a ProtocolResponse with a url and no session, Electron made the upstream request through defaultSession instead of the session that handled the protocol. A cached response could then be reused across otherwise isolated session partitions. Apps that use ProtocolResponse.url, omit ProtocolResponse.session, and rely on separate sessions to isolate content are affected. This issue is fixed in versions 40.10.6, 41.9.1, 42.5.1, and 43.0.0.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th 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-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control
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-70606 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70606?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70606?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-70606 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 40.10.6
electronjs:electronfrom 41.0.0 through 41.9.1
electronjs:electronfrom 42.0.0 through 42.5.1
electronjs:electron43.0.0:alpha1
electronjs:electron43.0.0:alpha2
electronjs:electron43.0.0:alpha3
electronjs:electron43.0.0:alpha4
electronjs:electron43.0.0:alpha5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r4w5-6pfg-jxp5npmelectron>=43.0.0-alpha.1 <43.0.043.0.0
GHSA-r4w5-6pfg-jxp5npmelectron>=42.0.0-alpha.1 <42.5.142.5.1
GHSA-r4w5-6pfg-jxp5npmelectron>=41.0.0-alpha.1 <41.9.141.9.1
GHSA-r4w5-6pfg-jxp5npmelectron>=40.0.0-alpha.1 <40.10.640.10.6

References

Check your stackJSON