Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.7amended

Electron: Local race condition in Squirrel.Mac update installation on macOS

CVE-2026-102672GHSA-vv43-5jgx-7qv8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 42.0.0-beta.2, 41.10.5, 39.8.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 39.8.10>= 40.0.0-alpha.1, < 41.10.5>= 42.0.0-alpha.1, < 42.0.0-beta.2
    Fixed in
    39.8.10, 41.10.5, 42.0.0-beta.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.7 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-102672: 0.09% estimated exploitation activity in the next 30 days; percentile 0.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact On macOS, Electron bundles the Squirrel.Mac auto-update framework, whose privileged ShipIt helper performs the final step of an update as root. A local attacker could cause that helper to overwrite a different application's files, as root, instead of the app that started the update. Exploitation requires local access to the machine. Apps are only affected on macOS if they ship Squirrel.Mac-based auto-updates. Apps on other platforms, or that do not use Squirrel.Mac auto-updates, are not affected. Workarounds There are no app side workarounds, you must update to a patched version of Electron. Fixed Versions 42.0.0-beta.2 41.10.5 39.8.10 For more information If you have any questions or comments about this advisory, email us at security@electronjs.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vv43-5jgx-7qv8

  2. Revision 2 · amended ·

    Amended from osv record GHSA-vv43-5jgx-7qv8

  3. Revision 1 · created ·

    Published from ghsa record GHSA-vv43-5jgx-7qv8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102672

Advisory: Electron: Local race condition in Squirrel.Mac update installation on macOS
IDs: CVE-2026-102672, GHSA-vv43-5jgx-7qv8
Record: https://patchnext.com/advisories/cve-2026-102672 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 42.0.0-beta.2, 41.10.5, 39.8.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 39.8.10; >= 40.0.0-alpha.1, < 41.10.5; >= 42.0.0-alpha.1, < 42.0.0-beta.2; fixed in 39.8.10, 41.10.5, 42.0.0-beta.2

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vv43-5jgx-7qv8 (GitHub-reviewed advisory GHSA-vv43-5jgx-7qv8 lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-beta.2)
- Verified: https://osv.dev/vulnerability/GHSA-vv43-5jgx-7qv8 (OSV record GHSA-vv43-5jgx-7qv8 lists affected ranges: npm electron >=0 =40.0.0-alpha.1 =42.0.0-alpha.1 <42.0.0-beta.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…