What is CVE-2026-102676?

### Impact A ` ` could enable Node.js integration in its Web Workers even when its embedder had Node.js integration disabled, giving guest content more privilege than the embedder allowed. Apps are only affected if they enable the ` ` tag and the embedder is unsandboxed. Apps that do not use ` `, or that keep the embedder sandboxed, are not affected. ### Workarounds Remove `nodeIntegrationInWorker` from the guest preferences in a `will-attach-webview` handler, or do not enable the ` ` tag when loading untrusted content. ### Fixed Versions * `44.0.0-beta.5`

How severe is CVE-2026-102676?

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

Which packages are affected by CVE-2026-102676?

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

How do I fix CVE-2026-102676?

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

How do I detect CVE-2026-102676 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-102676 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

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

No public exploit code has been indexed for CVE-2026-102676 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-102676?

CVE-2026-102676 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th 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-102676?

CVE-2026-102676 is classified as Improper Privilege Management (CWE-269), CWE-1188 (CWE-1188). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2026-102676 was published on September 29, 2026 and was last updated on October 2, 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-102676 — electron

HIGHFix: electron/electron@6462a2e

CVE-2026-102676 is a high-severity (CVSS 8.3) Improper Privilege Management vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions

Also known asGHSA-9qh4-3jw8-366w

Published

Sep 29, 2026

Updated

Oct 2, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-102676.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

Of 390,400 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

📦electron📦electron📦electron📦electron

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A <webview> could enable Node.js integration in its Web Workers even when its embedder had Node.js integration disabled, giving guest content more privilege than the embedder allowed.

Apps are only affected if they enable the <webview> tag and the embedder is unsandboxed. Apps that do not use <webview>, or that keep the embedder sandboxed, are not affected.

Workarounds

Remove nodeIntegrationInWorker from the guest preferences in a will-attach-webview handler, or do not enable the <webview> tag when loading 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-102676 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

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 an embedded <webview> guest can enable nodeIntegrationInWorker for background Web Workers even when Node.js integration is disabled in the unsandboxed embedder. Untrusted guest content loaded inside a web view can exploit this behavior to spawn a Node-enabled worker, bypassing host…

Workaround published by Red Hat

Disable the <webview> tag in application configurations or ensure the host embedder process remains strictly sandboxed.

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

Frequently Asked Questions

### Impact A `<webview>` could enable Node.js integration in its Web Workers even when its embedder had Node.js integration disabled, giving guest content more privilege than the embedder allowed. Apps are only affected if they enable the `<webview>` tag and the embedder is unsandboxed. Apps that do not use `<webview>`, or that keep the embedder sandboxed, are not affected. ### Workarounds Remove `nodeIntegrationInWorker` from the guest preferences in a `will-attach-webview` handler, or do not enable the `<webview>` tag when loading untrusted content. ### Fixed Versions * `44.0.0-beta.5`