Vulnerability in electron (CVE-2026-70603)
Summary
Vulnerability in electron (CVE-2026-70603). Confidential information can be exposed externally. Mitigation: upgrade to 39.8.6 or later.
Original description
The description as published by the source.
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 security@electronjs.org
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-70603 has been found in electron.
Confidential information can be exposed externally. CVSS score: 6.0/10.
What to do: upgrade electron to 39.8.6 or later.
If unsure, ask your IT team or search "electron CVE-2026-70603" on the vendor's site.
CVE-2026-70603 (electron) — CWE-20 / CVSS v3 6.0
Attack vector: local
Patched: 39.8.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in electron.
Check the vendor advisory for the affected versions of electron.
Severity: Medium (CVSS 6.0/10). Confidential information can be exposed externally.
Update to 39.8.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'electron' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'electron' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
electronを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade electron to 39.8.6ステージング環境で 39.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- patch security-advisories@github.com
- web github.com