Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.7

Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter

CVE-2026-70609GHSA-4f78-qhmw-8j8m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 42.0.0-beta.1, 41.2.0, 40.9.0, 39.8.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 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
    Fixed in
    39.8.7, 42.0.0-beta.1, 40.9.0, 41.2.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.7 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-70609: 0.53% estimated exploitation activity in the next 30 days; percentile 45.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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. Apps are only affected if untrusted input can reach the mode argument of openDevTools(), or if untrusted content can call openDevTools() on a <webview it embeds. Apps that only ever pass a fixed dock mode are not affected. Workarounds Only pass fixed, allowlisted values (right, bottom, undocked, detach) as the DevTools mode, and do not expose openDevTools to untrusted content. Fixed Versions 42.0.0-beta.1 41.2.0 40.9.0 39.8.7 For more information If you have any questions or comments about this advisory, email Electron at security@electronjs.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-4f78-qhmw-8j8m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-70609

Advisory: Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter
IDs: CVE-2026-70609, GHSA-4f78-qhmw-8j8m
Record: https://patchnext.com/advisories/cve-2026-70609 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 42.0.0-beta.1, 41.2.0, 40.9.0, 39.8.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 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; fixed in 39.8.7, 42.0.0-beta.1, 40.9.0, 41.2.0

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4f78-qhmw-8j8m (GitHub-reviewed advisory GHSA-4f78-qhmw-8j8m lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =41.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-beta.1)

Commands are suggestions: review each one before running it.

Loading voting…