Skip to content
Fencer Intel
medium 6.7

CVE-2026-102672 json

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

published last mo. modified 24d ago also EUVD-2026-98837 , GHSA-vv43-5jgx-7qv8

cvss
6.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.10, 41.10.5, and 42.0.0-beta.2, Electron applications on macOS that use Squirrel.Mac-based automatic updates are vulnerable to a local race in the privileged ShipIt helper. The helper did not bind the validated update target to one canonical application-bundle path for the full installation, allowing a local attacker to redirect the root-level write so that it overwrites another application's files instead of the application that initiated the update. Applications on other platforms and macOS applications that do not use Squirrel.Mac-based automatic updates are not affected. This issue is fixed in versions 39.8.10, 41.10.5, and 42.0.0-beta.2.

Patch / fix

  • npm electron 39.8.10, 41.10.5, 42.0.0-beta.2
  • mozilla firefox 39.8.10, 41.10.5, 42.0.0-beta.2
  • electronjs electron 39.8.10, 41.10.5, 42.0.0-beta.2
  • atom electron 39.8.10, 41.10.5, 42.0.0-beta.2

Is CVE-2026-102672 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-102672 updated cvss 6.7

electron: Electron: Arbitrary file overwrite via race condition in ShipIt update helper

  • Red Hat Build of Podman Desktop rh-podman-desktop, rh-podman-desktop.git
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
27d ago

Exploit prediction

0.09% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm electron
<39.8.10
>=40.0.0-alpha.1, <41.10.5
>=42.0.0-alpha.1, <42.0.0-beta.2
39.8.10
41.10.5
42.0.0-beta.2

Affected products

  • electron electron

Classification

Weakness
  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.