Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-102672

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

Overview

Published
13 Oct 2026
Modified
16 Oct 2026
Medium CVE
1 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.7 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Weakness: CWE-367

Affected packages · 1

Packages affected by CVE-2026-102672
EcosystemPackageVulnerableFixed 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.1041.10.542.0.0-beta.2

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.