CVE-2026-70606

Electron: ProtocolResponse.url reuses the default session cache instead of the registering session

MEDIUM

5.9

CVSS Score

Published: August 5, 2026 at 04:07 PM UTC

Updated: October 8, 2026 at 01:53 PM UTC

2 products affected across 2 vendorsElectronElectron

Using electron by electron?

Get instant alerts when new vulnerabilities affect electron - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.9

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Electron · Electronjsnpm

95%

v < 40.10.641.0.0 ≤ v ≤ 41.9.142.0.0 ≤ v ≤ 42.5.1*43.0.0 43.0.0 alpha1 43.0.0 alpha2 43.0.0 alpha3 43.0.0 alpha4 43.0.0 alpha5

Affected range stops below 40.10.6, so it looks safe — our inference, not a vendor statement

Electron · Electron

90%

>= 40.0.0-alpha.1, < 40.10.6>= 41.0.0-alpha.1, < 41.9.1>= 42.0.0-alpha.1, < 42.5.1>= 43.0.0-alpha.1, < 43.0.0

Affected range stops below 40.10.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 41.9.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 42.5.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 43.0.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/electron/electron/security/advisories/GHSA-r4w5-6pfg-jxp5

References (1)

x_refsource_CONFIRMVendor Advisory

Source: cverecord

https://github.com/electron/electron/security/advisories/GHSA-r4w5-6pfg-jxp5

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: HIGH
Privileges: NONE
User Interaction: REQUIRED
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-668

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card