Summary
Electron: ProtocolResponse.url reuses the default session cache instead of the registering session
Advisory details
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.042.5.141.9.140.10.6
For more information
If you have any questions or comments about this advisory, email Electron at security@electronjs.org
References
Related vulnerabilities
All Supply chain →- CRITICALCVE-2026-73843
OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs
- HIGHCVE-2026-53657
Lima: An arbitrary user in a QEMU VM could gain the root privilege in the VM via the guest agent socket
- MEDIUMGHSA-596p-6jv8-775v
Craft CMS: Authenticated leak of secret environment variables
- HIGHCVE-2026-67427
Flyto2 Core: ${env.VAR} interpolation reads any env secret despite env.get being denylisted
- HIGHCVE-2026-54727
proot-distro has a Container Isolation Bypass via Crafted Restore Archive
- HIGHCVE-2026-54504
@andrea9293/mcp-documentation-server: Web UI API binds to all interfaces without authentication by default