Improper Neutralization of Null Byte or NUL Character Affecting electron package, versions <39.8.6>=40.0.0-alpha.2 <40.9.1>=41.0.0-alpha.1 <41.1.1>=42.0.0-alpha.1 <42.0.0-beta.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-ELECTRON-18563328
- published6 Aug 2026
- disclosed5 Aug 2026
- creditYassine Bengana, Maxence Schmitt
Introduced: 5 Aug 2026
NewCVE-2026-70603 (opens in a new tab)How to fix?
Upgrade electron to version 39.8.6, 40.9.1, 41.1.1, 42.0.0-beta.1 or higher.
Overview
electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS.
Affected versions of this package are vulnerable to Improper Neutralization of Null Byte or NUL Character via the shell.openPath function. An attacker can bypass file path validation by supplying a path containing an embedded null byte, which may result in opening a different file than intended.
Note: This is only exploitable if paths derived from untrusted input are passed to shell.openPath and only string-based validation is performed without a filesystem check.
Workaround
This vulnerability can be mitigated by rejecting any path containing a null byte before passing it to shell.openPath.