dbcve.org
ElectronApplication · Electronjs

CVE-2026-34775

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-04
Fix available
A fix is available. Upgrade to 38.8.6 / 39.8.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0, the nodeIntegrationInWorker webPreference was not correctly scoped in all configurations. In certain process-sharing scenarios, workers spawned in frames configured with nodeIntegrationInWorker: false could still receive Node.js integration. Apps are only affected if they enable nodeIntegrationInWorker. Apps that do not use nodeIntegrationInWorker are not affected. This issue has been patched in versions 38.8.6, 39.8.4, 40.8.4, and 41.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The nodeIntegrationInWorker webPreference in Electron was not correctly scoped in certain process-sharing scenarios. Workers spawned in frames configured with nodeIntegrationInWorker: false could still receive Node.js integration, enabling potential remote code execution. Only apps that explicitly enable nodeIntegrationInWorker are affected.

MitigationUpgrade Electron to versions 38.8.6, 39.8.4, 40.8.4, or 41.0.0. If nodeIntegrationInWorker is not required, disable it in webPreferences to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ElectronApplication
Affected:< 38.8.6>= 39.0.0, < 39.8.4>= 40.0.0, < 40.8.4= 41.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Electron version
    Run 'electron --version' from the application directory, or check the electron version in package.json dependencies, or inspect the electron binary directly
    Affected if The version is less than 38.8.6, or between 39.0.0 and 39.8.4, or between 40.0.0 and 40.8.4, or exactly 41.0.0
  2. Identify webPreferences configuration
    Search codebase for 'nodeIntegrationInWorker' in BrowserWindow, session, or webview tag configurations
    Affected if nodeIntegrationInWorker is set to true in any webPreferences configuration
  3. Check for process-sharing contexts
    Inspect webPreferences for combinations that enable process sharing, such as contextIsolation: false, sandbox: false, or webSecurity: false in frames or webviews
    Affected if Process-sharing is enabled in frames where workers are spawned and nodeIntegrationInWorker setting may be incorrectly scoped
  4. Audit worker usage in frames
    Search for Web Worker creation (new Worker, SharedWorker) in iframes or webview elements within the application
    Affected if Workers are spawned in frames with nodeIntegrationInWorker: false but may still receive Node.js integration due to the scoping bug

You are affected if your Electron version is within the vulnerable range AND you use nodeIntegrationInWorker in any capacity OR have workers running in frames with process-sharing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 38.8.6 / 39.8.4 / 40.8.4 or later
Fixed in 38.8.639.8.440.8.4
Interim mitigation

Upgrade Electron to versions 38.8.6, 39.8.4, 40.8.4, or 41.0.0. If nodeIntegrationInWorker is not required, disable it in webPreferences to reduce attack surface.

Recommended fix High confidence

Electron 38.8.6 (if on 38.x), 39.8.4 (if on 39.x), 40.8.4 (if on 40.x), or 41.0.0 (if on 41.x)

  1. 1. Identify the current Electron version in your project by checking package.json or running 'npm list electron'
  2. 2. Determine which major version branch you are currently on (38.x, 39.x, 40.x, or 41.x)
  3. 3. Update the Electron version in your package.json to the patched version for your branch: for 38.x use 38.8.6, for 39.x use 39.8.4, for 40.x use 40.8.4, or for 41.x use 41.0.0
  4. 4. Run 'npm install' or 'npm update' to fetch the new Electron version
  5. 5. Rebuild any native modules compatible with Electron using 'electron-rebuild' if your project uses native dependencies
  6. 6. Test your application thoroughly, especially any code using nodeIntegrationInWorker or Web Workers
  7. 7. Verify that Node.js integration is correctly disabled in workers when nodeIntegrationInWorker: false is set
Caveat Electron major version upgrades may introduce breaking changes; review the Electron release notes for your target version for API changes and deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Electron Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data