Vulnerability in electron (CVE-2026-70597)
Summary
Vulnerability in electron (CVE-2026-70597). Confidential information can be exposed externally. Exploitable via ELECTRON_RUN_AS_NODE. Mitigation: upgrade to 42.0.0-beta.3 or later.
Original description
The description as published by the source.
Impact
On macOS, the check Electron uses to confirm it was launched by a same-signed parent process could be bypassed by a local process. Apps that enable the fuse-based hardening restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS to same-signed parents rely on this check; a local attacker could bypass it and run their own code inside the signed app, inheriting its TCC permissions and keychain access.
Apps are only affected if they enable those macOS fuse-based restrictions. Apps that do not enable them are not affected.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
42.0.0-beta.341.2.140.9.039.8.8
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-70597 has been found in electron.
Attackers can target a specific entry point like ELECTRON_RUN_AS_NODE over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade electron to 42.0.0-beta.3 or later.
If unsure, ask your IT team or search "electron CVE-2026-70597" on the vendor's site.
CVE-2026-70597 (electron) — CWE-367 / CVSS v3 6.3
Attack vector: local / no user interaction
Attack surface: ELECTRON_RUN_AS_NODE / NODE_OPTIONS
Patched: 42.0.0-beta.3 — apply immediately
Workaround: There are no app side workarounds, you must update to a patched version of Electron.
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-367) exists in electron. Attackers reach the vulnerable code path via ELECTRON_RUN_AS_NODE.
Check the vendor advisory for the affected versions of electron. Attack surface: ELECTRON_RUN_AS_NODE / NODE_OPTIONS.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 42.0.0-beta.3.
Workaround: There are no app side workarounds, you must update to a patched version of Electron.
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 temporary workaround mitigate
There are no app side workarounds, you must update to a patched version of Electron.パッチが適用されるまでの応急処置として、There are no app side workarounds, you must update to a patched version of Electron. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade electron to 42.0.0-beta.3ステージング環境で 42.0.0-beta.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com