# CVE-2026-70612: electron — Fixed in 39.8.8

📦

📦 npm

Not in CISA KEV

MEDIUM severity

# CVE-2026-70612 — electron

MEDIUM [Fix: electron/electron@08b9d0a](https://github.com/electron/electron/commit/08b9d0a220e267d1a2402a44bdd01a2e9aa320b5)

CVE-2026-70612 is a medium-severity (CVSS 5.4) CWE-284 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: Sandboxed iframes can launch external protocol handlers

Also known as[GHSA-p2rr-rvmm-c5fp](/vulnerability/GHSA-p2rr-rvmm-c5fp)

Published

Aug 5, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-70612.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

0.00%0.32%0.63%0.95%0.5%0.4%0.4%0.4%Sep 26Nov 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`electron`npm

12.3Mdownloads / week

## Description

#### Impact

Requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame's sandbox state was also not made available to the app's permission handlers.

Apps are only affected if they render untrusted content in sandboxed iframes and grant the `openExternal` permission (granted by default when no `setPermissionRequestHandler` is installed). Apps whose permission handler denies `openExternal` for untrusted content are not affected.

#### Workarounds

Install a `setPermissionRequestHandler` that denies the `openExternal` permission for untrusted content.

#### Fixed Versions

-   `42.0.0-beta.3`
-   `41.2.1`
-   `40.9.0`
-   `39.8.8`

#### For more information

If you have any questions or comments about this advisory, email Electron at [security@electronjs.org](mailto:security@electronjs.org)

## Affected Packages

4 total 4 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`electron` 

all versions

39.8.8`npm install electron@39.8.8`

📦npm

`electron` 

≥ 40.0.0-alpha.1&&< 40.9.0

40.9.0`npm install electron@40.9.0`

📦npm

`electron` 

≥ 41.0.0-alpha.1&&< 41.2.1

41.2.1`npm install electron@41.2.1`

📦npm

`electron` 

≥ 42.0.0-alpha.1&&< 42.0.0-beta.3

42.0.0-beta.3`npm install electron@42.0.0-beta.3`

## Affected Products

1 product · 11 configurations

Application

`electron`electronjs

≥ 41.0.0 && ≤ 41.2.1

1 version

42.0.0

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update electron to 39.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-70612 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
    

## Frequently Asked Questions

\### Impact Requests to open external protocol URLs from web content did not take iframe sandbox restrictions into account, so a sandboxed iframe could cause an OS-registered external application to be launched. The frame's sandbox state was also not made available to the app's permission handlers. Apps are only affected if they render untrusted content in sandboxed iframes and grant the \`openExternal\` permission (granted by default when no \`setPermissionRequestHandler\` is installed). Apps whose permission handler denies \`openExternal\` for untrusted content are not affected. ### Workarounds I

O3 Security · Impact-Aware SCA

### Is CVE-2026-70612 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)