Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:LSummary
CVE-2026-34779 is a medium-severity OS Command Injection (CWE-78) vulnerability in Electronjs Electron. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 6th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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-34779 is a vulnerability in the Electron framework, which enables development of cross-platform desktop applications using JavaScript, HTML, and CSS. On macOS, versions prior to 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8 are affected when applications invoke the app.moveToApplicationsFolder() API. This method employs an AppleScript fallback that inadequately handles certain characters in the application bundle path, potentially enabling arbitrary AppleScript execution under specific conditions. Applications not using this API remain unaffected. The issue is classified under CWE-78 (OS Command Injection) with a CVSS v3.1 base score of 6.5 (AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L).
Exploitation requires local access (AV:L) with no privileges (PR:N), high attack complexity (AC:H), and user interaction (UI:R), such as accepting a move-to-Applications prompt. An attacker could craft a malicious launch path for the application, leveraging the flawed AppleScript handling to execute arbitrary commands on the system. Successful exploitation yields high impacts on confidentiality and integrity (C:H/I:H), with low availability impact (A:L), potentially allowing data exfiltration, modification, or other system compromise depending on the executed AppleScript.
The Electron security advisory (GHSA-5rqw-r77c-jp79) confirms patches in versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8, recommending immediate upgrades for affected applications. Developers should verify usage of app.moveToApplicationsFolder() and apply the fixes to mitigate risks on macOS deployments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18957
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.1, 40.8.0, and 41.0.0-beta.8, on macOS, app.moveToApplicationsFolder() used an AppleScript fallback path that did not properly handle certain characters in the application…
more
bundle path. Under specific conditions, a crafted launch path could lead to arbitrary AppleScript execution when the user accepted the move-to-Applications prompt. Apps are only affected if they call app.moveToApplicationsFolder(). Apps that do not use this API are not affected. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.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.5V1.2.8V15.2.5
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect command sanitization during development.
Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.
Least privilege reduces the permissions available to any process that could be subverted by injected commands.
Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.
Secure engineering principles require proper neutralization of untrusted input before command construction.
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.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
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 and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.