CVE-2026-34769
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 · uneditedElectron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, an undocumented commandLineSwitches webPreference allowed arbitrary switches to be appended to the renderer process command line. Apps that construct webPreferences by spreading untrusted configuration objects may inadvertently allow an attacker to inject switches that disable renderer sandboxing or web security controls. Apps are only affected if they construct webPreferences from external or untrusted input without an allowlist. Apps that use a fixed, hardcoded webPreferences object are not affected. This issue has been patched in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8.
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 confidenceElectron versions prior to 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8 contain an undocumented 'commandLineSwitches' webPreference that allows arbitrary command-line switches to be appended to the renderer process. When applications construct webPreferences from untrusted external input without an allowlist, attackers can inject switches that disable renderer sandboxing or web security controls.
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< 38.8.6>= 39.0.0, < 39.8.0>= 40.0.0, < 40.7.0= 41.0.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Electron versionRun 'npm list electron' in the project directory, or check package.json for the electron version dependency, or run 'electron --version' if electron is installed globallyAffected if The version is less than 38.8.6, OR between 39.0.0 and 39.8.0 exclusive, OR between 40.0.0 and 40.7.0 exclusive, OR exactly 41.0.0 (non-beta)
-
Search for webPreferences construction in source codeSearch the codebase for patterns like 'webPreferences' or 'new BrowserWindow' to find where webPreferences are definedAffected if webPreferences are built using data from external or untrusted sources (query parameters, user input, environment variables from external sources)
-
Inspect for commandLineSwitches usageSearch the codebase for the string 'commandLineSwitches' in JavaScript/TypeScript filesAffected if The string 'commandLineSwitches' appears in any webPreferences configuration
-
Check for allowlist validation on webPreferencesReview the code that constructs webPreferences to see if there is an explicit allowlist of allowed preference keys, or if the preferences are passed directly from external inputAffected if webPreferences are constructed directly from external input without filtering to a fixed allowlist of known-safe preference names
-
Audit BrowserWindow creation callsExamine all BrowserWindow and webContents.createBrowserWindow calls in the application code, looking for any that accept webPreferences from external sourcesAffected if Any BrowserWindow is created with webPreferences derived from untrusted external input without allowlisting
You are affected if your Electron version falls within the vulnerable ranges AND your application constructs webPreferences from untrusted external input without using an allowlist to restrict which preferences are accepted.
Generated from the published advisory. Verify against your own configuration.
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 · scoped38.8.639.8.040.7.0
Avoid constructing webPreferences from external or untrusted input; use fixed, hardcoded webPreferences objects or implement strict allowlisting. Upgrading to the patched versions (38.8.6, 39.8.0, 40.7.0, or 41.0.0-beta.8) is recommended.
Electron 38.8.6, 39.8.0, 40.7.0, or 41.0.0+ (depending on your current major version branch)
- Identify the current Electron version in use (check package.json or node_modules/electron/package.json)
- Determine which major version branch you are on: 38.x, 39.x, 40.x, or 41.x
- Upgrade to the appropriate fixed version: 38.8.6 (for 38.x branch), 39.8.0 (for 39.x branch), 40.7.0 (for 40.x branch), or 41.0.0+ (for 41.x branch)
- Update the package.json version and run npm install or yarn install to fetch the patched version
- If you construct webPreferences from external or untrusted input, implement an allowlist of allowed options to prevent injection of undocumented switches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34769 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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