CVE-2026-34769: Electron: Renderer command-line switch injection via undocumented commandLineSwitches webPreference
Electron 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.
Security readout for executives and security teams
Plain-English summary
This affects some Electron desktop apps, not every Electron installation. If an app lets untrusted configuration flow into webPreferences, an attacker could add renderer command-line switches that weaken sandboxing or web security. Electron has fixed the issue in supported patched versions.
Executive priority
Treat as high priority for organizations building or distributing Electron desktop apps, especially configurable clients. Patch internal builds promptly and require vendor statements for third-party Electron apps. Broad emergency response is not supported by the provided evidence without confirmed exploitation.
Technical view
An undocumented commandLineSwitches webPreference allowed arbitrary renderer process switches before Electron 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8. Exposure depends on applications spreading external or untrusted objects into webPreferences without an allowlist. Fixed, hardcoded webPreferences objects are not affected.
Likely exposure
Likely limited to Electron applications that accept plugin, workspace, user, or remote configuration and merge it into webPreferences. Organizations using packaged Electron apps need vendor confirmation; internally built Electron apps should be reviewed directly. Hardcoded webPreferences materially reduce exposure.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. CVSS indicates local attack vector, high complexity, no privileges required, and user interaction required. The practical risk is highest where attacker-controlled configuration can influence Electron window creation.
Researcher notes
Focus triage on data flow into webPreferences, not just Electron version presence. The vulnerable pattern is untrusted object spreading or equivalent dynamic construction. The provided sources identify affected Electron ranges and patched versions, but do not provide product-specific downstream exposure.
Mitigation direction
Upgrade Electron to 38.8.6, 39.8.0, 40.7.0, 41.0.0-beta.8, or later.
Audit webPreferences construction and remove spreading of untrusted configuration objects.
Use an explicit allowlist for accepted webPreferences keys.
Reject or ignore commandLineSwitches in externally supplied configuration.
Ask third-party Electron application vendors for CVE-2026-34769 status.
Validation and detection
Inventory Electron versions used by internal and packaged desktop applications.
Review BrowserWindow creation paths for external data reaching webPreferences.
Confirm webPreferences are fixed or built from an explicit allowlist.
Check dependency lockfiles and packaged artifacts for patched Electron versions.
Document vendor responses for third-party Electron-based applications.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-88: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-88 · source CWE mapping
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Hidden Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.