CVE-2026-70603: Electron: shell.openPath path validation bypass via embedded null byte
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.
Published Aug 5, 2026
Affected packages
electron
- Ecosystem
- npm
- Affected
- >= 42.0.0-alpha.1, < 42.0.0-beta.1
- Fixed in
- 42.0.0-beta.1
- Check
npm ls electron
electron
- Ecosystem
- npm
- Affected
- >= 41.0.0-alpha.1, < 41.1.1
- Fixed in
- 41.1.1
- Check
npm ls electron
electron
- Ecosystem
- npm
- Affected
- >= 40.0.0-alpha.1, < 40.9.0
- Fixed in
- 40.9.0
- Check
npm ls electron
electron
- Ecosystem
- npm
- Affected
- < 39.8.6
- Fixed in
- 39.8.6
- Check
npm ls electron
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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():
if (filePath.includes('\0')) throw new Error('invalid path');Fixed Versions
42.0.0-beta.141.1.140.9.039.8.6
For more information
If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected])
Credited to yassine-doyensec, ikkisoft, maxence-Doyensec.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-115570
Electron: Mitigation for compromised eMudhra intermediate certificates
high7.4Oct 23, 2026CVE-2026-113796
Electron: SameSite cookie restrictions are not applied to windows opened from links
medium4.2Oct 22, 2026CVE-2026-113797
Electron: Extension tabs.query returns tab URLs and titles without the tabs permission
low3.1Oct 22, 2026CVE-2026-113798
Electron: Pointer lock permission requests can be attributed to the wrong frame
medium5.4Oct 22, 2026CVE-2026-114121
Electron: openExternal permission requests can be attributed to the wrong origin
medium5.4Oct 22, 2026CVE-2026-114122
Electron: Frame subscription trusts GPU-supplied frame geometry
low3.9Oct 22, 2026
