CVE-2026-34769
Electronjs Electron ≤ 38.8.6
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2026-34769 is a high-severity Argument Injection (CWE-88) vulnerability in Electronjs Electron. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-34769 affects the Electron framework, which enables development of cross-platform desktop applications using JavaScript, HTML, and CSS. In versions prior to 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, an undocumented webPreference named commandLineSwitches permits arbitrary switches to be appended to the renderer process command line. This vulnerability impacts Electron-based applications that construct webPreferences by spreading untrusted configuration objects, without implementing an allowlist, potentially enabling attackers to inject switches that disable critical protections such as renderer sandboxing or web security controls. Applications using fixed, hardcoded webPreferences remain unaffected.
Exploitation requires local access (AV:L), high attack complexity (AC:H), no privileges (PR:N), and user interaction (UI:R), with a CVSS v3.1 base score of 7.7 indicating high severity due to changed scope (S:C) and high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H). An attacker could supply malicious configuration data—such as through external inputs or tampered files—to an affected application, tricking a user into loading it. Successful exploitation allows bypassing sandboxing and security features in the renderer process, potentially leading to arbitrary code execution or data exfiltration within the application's context. The issue maps to CWE-88 (Improper Neutralization of Argument Delimiters in a Command) and CWE-912 (Hidden Functionality).
The Electron security advisory (GHSA-9wfr-w7mm-pc7f) confirms patches in versions 38.8.6, 39.8.0, 40.7.0, and 41.0.0-beta.8, recommending that developers avoid spreading untrusted objects into webPreferences and instead use hardcoded configurations or strict allowlists for any dynamic inputs to prevent switch injection.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18937
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.5
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing can discover argument-injection flaws in command-construction code but does not stop their introduction.
Input validation directly stops construction of command strings containing unneutralized delimiters or injected arguments.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect argument injection but does not prevent it at the source.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development lifecycle mandates input validation and command construction practices that directly prevent argument injection.
Application security requirements include explicit rules for safe command-line argument handling and escaping.
Secure architecture principles discourage unsafe command invocation patterns and favor safer APIs.