Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictionsGHSA-9qh4-3jw8-366w

HIGHFix: electron/electron@6462a2e

GHSA-9qh4-3jw8-366w 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.

Also known asCVE-2026-102676
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 16, 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 GHSA-9qh4-3jw8-366w.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.5%0.5%Oct 26Oct 26

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

How urgent is this, really

GHSA-9qh4-3jw8-366w 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

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
8.1Mdownloads / week

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
EcosystemPackageVulnerable rangeFix
📦npmelectronall versions41.10.6npm install electron@41.10.6
📦npmelectron≥ 42.0.0-alpha.1&&< 42.9.242.9.2npm install electron@42.9.2
📦npmelectron≥ 43.0.0-alpha.1&&< 43.4.143.4.1npm install electron@43.4.1
📦npmelectron≥ 44.0.0-alpha.1&&< 44.0.0-beta.544.0.0-beta.5npm 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

  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 41.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qh4-3jw8-366w is resolved across your whole dependency graph.

  3. 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 GHSA-9qh4-3jw8-366w (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`
O3 Security · Impact-Aware SCA

Is GHSA-9qh4-3jw8-366w in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Electron: <webview> can enable Node.js integration in…