Skip to content
Fencer Intel
medium 5.7

CVE-2026-70609 json

Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter

published 3mo ago modified last mo. also EUVD-2026-53566 , GHSA-4f78-qhmw-8j8m

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.7, 40.9.0, 41.2.0, and 42.0.0-beta.1, the mode option of webContents.openDevTools() was not sanitized before use by the DevTools frontend. If an attacker can influence this value, script under their control may run in the DevTools context, which in unsandboxed configurations has access to Node.js, including when untrusted input reaches the mode argument of openDevTools() or untrusted content calls openDevTools() on a webview it embeds. This issue is fixed in 39.8.7, 40.9.0, 41.2.0, and 42.0.0-beta.1.

Patch / fix

  • npm electron 39.8.7, 40.9.0, 41.2.0, 42.0.0-beta.1
  • atom electron 39.8.7, 40.9.0, 41.2.0, 42.0.0-beta.1
  • electronjs electron 39.8.7, 40.9.0, 41.2.0, 42.0.0-beta.1

Is CVE-2026-70609 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
3mo ago

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm electron
<39.8.7
>=40.0.0-alpha.1, <40.9.0
>=41.0.0-alpha.1, <41.2.0
>=42.0.0-alpha.1, <42.0.0-beta.1
39.8.7
40.9.0
41.2.0
42.0.0-beta.1

Affected products

  • electron electron

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of electron/electron published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.