GHSA-r4w5-6pfg-jxp5: Electron: ProtocolResponse.url reuses the default session cache instead of the registering session
Impact
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. Apps that set an explicit session, or that do not isolate content across sessions, are not affected.
Workarounds
Set ProtocolResponse.session explicitly so the request uses the intended session's cache.
Fixed Versions
- 43.0.0
- 42.5.1
- 41.9.1
- 40.10.6
For more information
If you have any questions or comments about this advisory, email Electron at security@electronjs.org
Details
Original advisory: https://github.com/advisories/GHSA-r4w5-6pfg-jxp5
Referenced CVEs
| CVE | CSIRTS overview | External |
|---|---|---|
| CVE-2026-70606 | coverage & exploitation status | NVD · CVE.org |
Same CVEs, other sources
How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.
More from GitHub Security Advisories
- mediumGHSA-v93f-fgjr-hjrj: Electron: window.open features string controls some window options considered privileged2026-08-05
- mediumGHSA-v64r-4m7r-3mvq: Electron: HTTP redirect followed into local file loader2026-08-05
- highGHSA-v3j7-r9gq-3gjw: Electron: Custom protocol with supportFetchAPI but not corsEnabled allows cross-origin re…2026-08-05
- mediumGHSA-m55f-7gqj-fr98: Electron: Extension tab APIs operate across session boundaries2026-08-05
- mediumGHSA-5c9j-mhmv-5xgx: Electron: shell.openPath path validation bypass via embedded null byte2026-08-05