How severe is CVE-2026-102674?

CVE-2026-102674 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-102674?

CVE-2026-102674 affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix CVE-2026-102674?

Update electron to 41.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102674 is resolved across your whole dependency graph.

How do I detect CVE-2026-102674 in my npm dependencies?

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.

How do I mitigate CVE-2026-102674 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-102674 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-102674 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-102674?

CVE-2026-102674 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-102674?

CVE-2026-102674 is classified as CWE-266 (CWE-266), CWE-693 (CWE-693). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-102674 published, and has it been updated?

CVE-2026-102674 was published on September 29, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2026-102674 — electron

HIGHFix: electron/electron@29fc130

CVE-2026-102674 is a high-severity (CVSS 8.2) CWE-266 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions

Also known asGHSA-gr2m-v5gq-v685

Published

Sep 29, 2026

Updated

Oct 21, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 23, 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-102674.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.03%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-102674 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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

electronnpm

5.3Mdownloads / week

Description

Impact

Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes.

Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected.

Workarounds

Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.

Fixed Versions

44.0.0-beta.5
43.4.1
42.9.2
41.10.6

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	all versions	41.10.6`npm install electron@41.10.6`
📦npm	`electron`	≥ 42.0.0-alpha.1&&< 42.9.2	42.9.2`npm install electron@42.9.2`
📦npm	`electron`	≥ 43.0.0-alpha.1&&< 43.4.1	43.4.1`npm install electron@43.4.1`
📦npm	`electron`	≥ 44.0.0-alpha.1&&< 44.0.0-beta.5	44.0.0-beta.5`npm install electron@44.0.0-beta.5`

Affected Products

1 product · 16 configurations

Application

electronelectronjs

≥ 43.0.0 && < 43.4.1

1 version

44.0.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update electron to 41.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-102674 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in Electron where child windows opened from a sandboxed top-level document fail to inherit the document's active HTML sandbox restrictions. An attacker capable of delivering untrusted content to a sandboxed document that is permitted to open popups can spawn a window running under the application's…

Workaround published by Red Hat

Applications can mitigate this vulnerability by intercepting and denying unexpected popups using setWindowOpenHandler. Returning { action: 'deny' } for unvalidated or unapproved popup requests prevents child windows from opening with the full origin context.

Source: Red Hat security advisory for CVE-2026-102674 (CC BY 4.0)

Frequently Asked Questions

### Impact Windows opened from a sandboxed top-level document did not inherit that document's HTML `sandbox` restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes. Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with `setWindowOpenHandler` are not affected. ### Workarounds Return `{ action: 'deny' }` from `setWindowOpenHandler` for windows opened by untrusted content. ##