CVE-2026-70606

mediumpriority · track · 0EPSS 0.003 · 17 %ileEUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.26% (17th) EPSS

CVSS 5.9 · medium

Is it mine?

12 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

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.

cvss

Technical severity, 0–10. One row per scoring source.

5.9

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:Nsecondary · ENISA EU

v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:Nsecondary · security-advisories@github.comexploitability 1.6 · impact 4.2

v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:Nsecondary · OSV

v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-668USCWE-668US

affected products (12)

Products and version ranges known to be affected.

Electron Electron40.0.0-alpha.1, → 40.10.6enisa_euvdEU
Electron Electron41.0.0-alpha.1, → 41.9.1enisa_euvdEU
Electron Electron42.0.0-alpha.1, → 42.5.1enisa_euvdEU
Electron Electron43.0.0-alpha.1, → 43.0.0enisa_euvdEU
electronjs electron< 40.10.6nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron41.0.0 → 41.9.1nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron42.0.0 → 42.5.1nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
electronjs electron= 43.0.0nvdUScpe:2.3:a:electronjs:electron:*:*:*:*:*:*:*:*
npm electron40.0.0-alpha.1 → 40.10.6osvUSpkg:npm/electron
npm electron41.0.0-alpha.1 → 41.9.1osvUSpkg:npm/electron
npm electron42.0.0-alpha.1 → 42.5.1osvUSpkg:npm/electron
npm electron43.0.0-alpha.1 → 43.0.0osvUSpkg:npm/electron

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-r4w5-6pfg-jxp5Electron: ProtocolResponse.url reuses the default session cache instead of the registering session2026-08-05ghsa · osvUS
### 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](mailto:security@electronjs.org)

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2026-08-05modified 2026-08-05

references (4)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan