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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.9 · electronjsNVD modified 2026-10-08 13:53
Affected (CPE criteria) 6
cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:43.0.0:alpha1:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:43.0.0:alpha2:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:43.0.0:alpha3:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:43.0.0:alpha4:*:*:*:node.js:*:*cpe:2.3:a:electronjs:electron:43.0.0:alpha5:*:*:*:node.js:*:*