Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 6.0 MEDIUMEUVD CVSS 3.1 6.0 CVSS 3.1 · [email protected] · Secondary 6.0 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by electron 42.0.0-beta.1Fixed by electron 41.1.1Fixed by electron 40.9.0Fixed by electron 39.8.6KEV status unknown

cve-program · CVE-2026-70603

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-53436

Published

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.

Read the publisher's advisory

nvd · CVE-2026-70603

Published

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.

Read the publisher's advisory

osv · GHSA-5c9j-mhmv-5xgx

Published

### Impact `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. Node's `fs` APIs already reject paths containing null bytes, so apps that call `fs.existsSync()`, `fs.stat()`, or similar before `shell.openPath()` are not affected. Apps that do not call `shell.openPath()` with untrusted input are not affected. ### Workarounds Reject any path containing a null byte before passing it to `shell.openPath()`: ```js if (filePath.includes('\0')) throw new Error('invalid path'); ``` ### Fixed Versions * `42.0.0-beta.1` * `41.1.1` * `40.9.0` * `39.8.6` ### For more information If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-70603

Published

electron

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "electron",
                    "product": "electron",
                    "versions": [
                        {
                            "version": "< 39.8.6",
                            "status": "affected"
                        },
                        {
                            "version": ">= 40.0.0-alpha.1, < 40.9.0",
                            "status": "affected"
                        },
                        {
                            "version": ">= 41.0.0-alpha.1, < 41.1.1",
                            "status": "affected"
                        },
                        {
                            "version": ">= 42.0.0-alpha.1, < 42.0.0-beta.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-53436

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 5, 2026, 3:56:50 PM

dateUpdated: Nov 3, 2026, 10:13:31 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-70603

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-20 · CWE-158

Original publisher date fields

published: 2026-08-05T16:17:04.470

lastModified: 2026-11-03T23:17:53.147

8 source CPE criteria · context only
  • cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha2:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha3:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha4:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha5:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:alpha6:*:*:*:node.js:*:*
  • cpe:2.3:a:electronjs:electron:42.0.0:beta1:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-5c9j-mhmv-5xgx

Published

electron

npm

SEMVER · introduced 42.0.0-alpha.1 → fixed 42.0.0-beta.1

electron

npm

SEMVER · introduced 41.0.0-alpha.1 → fixed 41.1.1

electron

npm

SEMVER · introduced 40.0.0-alpha.1 → fixed 40.9.0

electron

npm

SEMVER · introduced 0 → fixed 39.8.6

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 19:43 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current