Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior…
Historical advisory recorded 4 Nov 2026 19:04:27 UTC. Read the latest advisory.
nvd · CVE-2026-70603
PublishedElectron 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 advisoryAffected versions, risk and source history
nvd · CVE-2026-70603
PublishedElectron 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 perf…
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.
Additional publisher context
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.
- Source published
- 5 Aug 2026 16:17:04 UTC
- Source modified
- 3 Nov 2026 23:17:53 UTC
- Saved here
- 4 Nov 2026 19:04:27 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 6.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N