PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-34779 Electronjs CVE debrief

The Electron framework, used for building cross-platform desktop applications, had a vulnerability prior to versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8. On macOS, the app.moveToApplicationsFolder() function used an AppleScript fallback path that did not properly handle certain characters in the application bundle path. This could lead to arbitrary AppleScript execution if a user accepted the move-to-Applications prompt and the application was crafted with a specific launch path.

Vendor
Electronjs
Product
Electron
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-04
Original CVE updated
2026-07-24
Advisory published
2026-04-04
Advisory updated
2026-07-24

Who should care

Developers using the Electron framework to build desktop applications, especially those deploying on macOS, should be aware of this vulnerability. If an application's path is not properly sanitized and it uses the app.moveToApplicationsFolder() API, it may be vulnerable to this exploit.

Technical summary

The vulnerability exists in the app.moveToApplicationsFolder() function in Electron. When this function is called on macOS, it uses an AppleScript fallback. However, the path to the application bundle was not properly sanitized, allowing for potential execution of arbitrary AppleScript code when a user interacts with the move-to-Applications prompt. The vulnerability is rated with a CVSS score of 6.5 and a severity of MEDIUM.

Defensive priority

Medium priority for Electron developers, especially those with applications on macOS that use the app.moveToApplicationsFolder() API.

Recommended defensive actions

  • Update Electron to version 38.8.6, 39.8.1, 40.8.0, or 41.0.0-beta.8 or later.
  • Review application code to ensure proper sanitization of paths used with app.moveToApplicationsFolder().
  • Implement additional monitoring for suspicious AppleScript execution in your application environment.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record was published on 2026-04-04T00:16:19.213Z and last modified on 2026-07-24T22:10:00.140Z. The vulnerability has been patched in the mentioned Electron versions. The CVSS vector is CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-34779 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-34779

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-34779 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34779

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.