Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior…
Historical advisory recorded 25 Oct 2026 15:18:57 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
PublishedNVD 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-10-08T13:54:00.020
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