# CVE-2026-70603: Electron: shell.openPath path validation bypass via embedded null byte > Attackers can bypass path validation in Electron apps using null bytes to open unintended files, potentially leading to code execution or data exposure. - **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 5 Aug 2026 - **Updated:** 6 Aug 2026 - **Also known as:** GHSA-5c9j-mhmv-5xgx ## What is CVE-2026-70603? CVE-2026-70603 is a medium-severity path traversal vulnerability in Electronjs Electron, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-20 (Improper Input Validation), CWE-158 (Improper Neutralization of Null Byte or NUL Character) ## Which versions are affected by CVE-2026-70603? 8 open source packages ship an affected version, including electron. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `electron` | npm | All versions | 39.8.6 | | `electron` | npm | All versions | 39.8.6 | | `electron` | npm | From 40.0.0-alpha.1 | 40.9.0 | | `electron` | npm | From 40.0.0-alpha.1 | 40.9.0 | | `electron` | npm | From 41.0.0-alpha.1 | 41.1.1 | | `electron` | npm | From 41.0.0-alpha.1 | 41.1.1 | | `electron` | npm | From 42.0.0-alpha.1 | 42.0.0-beta.1 | | `electron` | npm | From 42.0.0-alpha.1 | 42.0.0-beta.1 | Products: Electronjs Electron. ## How do I fix CVE-2026-70603? Upgrade electron to a fixed version for your release line: 39.8.6, 40.9.0, 41.1.1 or 42.0.0-beta.1. ## Is CVE-2026-70603 being exploited? There is no known exploitation of CVE-2026-70603 in the wild and no public exploit code. ## Other vulnerabilities in Electronjs Electron - [CVE-2017-16151](https://insights.sbomify.com/CVE-2017-16151/): Chromium Remote Code Execution in electron (critical 9.8) - [CVE-2018-1000118](https://insights.sbomify.com/CVE-2018-1000118/): Electron protocol handler browser vulnerable to Command Injection (high 8.8) - [CVE-2026-34780](https://insights.sbomify.com/CVE-2026-34780/): Electron: Context Isolation bypass via contextBridge VideoFrame transfer (high 8.4) - [CVE-2026-102676](https://insights.sbomify.com/CVE-2026-102676/): Electron: can enable Node.js integration in Web Workers despite embedder restrictions (high 8.3) - [CVE-2026-102673](https://insights.sbomify.com/CVE-2026-102673/): Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-70603 and fix it if it is affected. What it is: CVE-2026-70603 is a medium-severity path traversal vulnerability in Electronjs Electron, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-70603 in the wild and no public exploit code. Affected packages and fixed versions: - electron (npm): affected all versions; fixed in 39.8.6 - electron (npm): affected all versions; fixed in 39.8.6 - electron (npm): affected from 40.0.0-alpha.1; fixed in 40.9.0 - electron (npm): affected from 40.0.0-alpha.1; fixed in 40.9.0 - electron (npm): affected from 41.0.0-alpha.1; fixed in 41.1.1 - electron (npm): affected from 41.0.0-alpha.1; fixed in 41.1.1 - electron (npm): affected from 42.0.0-alpha.1; fixed in 42.0.0-beta.1 - electron (npm): affected from 42.0.0-alpha.1; fixed in 42.0.0-beta.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-70603/ (Markdown: https://insights.sbomify.com/CVE-2026-70603/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70603 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70603 - OSV: https://osv.dev/vulnerability/CVE-2026-70603 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-70603/ Summaries are generated and may contain mistakes; the official description above is the record.