CVE-2026-70603

Electron: shell.openPath path validation bypass via embedded null byte

MEDIUM

CVSS Score

Published: August 5, 2026 at 03:56 PM UTC

Updated: October 8, 2026 at 01:54 PM UTC

2 products affected across 2 vendorsElectronElectron

Using electron by electron?

Get instant alerts when new vulnerabilities affect electron - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6

Exploit prediction

EPSS 0.1%

SSVC

No known exploit

Description

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1, shell.openPath() did not reject paths containing embedded null bytes. Apps that perform string-only validation of file paths, for example checking the file extension, before passing them to shell.openPath() could be bypassed, allowing an attacker-controlled path to open a different file than the one that passed validation. Apps are only affected if they pass paths derived from untrusted input to shell.openPath() and rely on string-based validation without a filesystem check. This issue is fixed in versions 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Electron · Electronjsnpm

95%

v < 39.8.640.0.0 ≤ v < 40.9.041.0.0 ≤ v < 41.1.1*42.0.0 42.0.0 alpha1 42.0.0 alpha2 42.0.0 alpha3 42.0.0 alpha4 42.0.0 alpha5 42.0.0 alpha6 42.0.0 beta1

Affected range stops below 39.8.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 40.9.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 41.1.1, so it looks safe — our inference, not a vendor statement

Electron · Electron

90%

v < 39.8.6>= 40.0.0-alpha.1, < 40.9.0>= 41.0.0-alpha.1, < 41.1.1>= 42.0.0-alpha.1, < 42.0.0-beta.1

Affected range stops below 39.8.6, so it looks safe — our inference, not a vendor statement

Affected range stops below 40.9.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 41.1.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 42.0.0-beta.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://github.com/electron/electron/security/advisories/GHSA-5c9j-mhmv-5xgx

References (1)

x_refsource_CONFIRMVendor Advisory

Source: cverecord

https://github.com/electron/electron/security/advisories/GHSA-5c9j-mhmv-5xgx

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6MEDIUMGitHub_M

Attack Vector: LOCAL
Complexity: HIGH
Privileges: LOW
User Interaction: REQUIRED
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-20CWE-158

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card