Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, the check Electron uses on macOS to confirm it was launched by a same-signed parent process could be bypassed by a local process. Apps that enable fuse-based hardening restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS to same-signed parents rely on this check, and a local attacker could bypass it and run code inside the signed app, inheriting its TCC permissions and keychain access. This issue is fixed in 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
CVE-2026-70597
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 6, 2026
Advisory Details (2)
Auto-updated Aug 5, 2026commit 0a6291a97d21 (electron/electron)
Fix landed in electron/electron commit 0a6291a97d21 — awaiting tagged release
https://github.com/electron/electron/commit/0a6291a97d210db3733689e70a51f5711e38ed35Parent process code-sign check is spoofable · Advisory · electron/electron · GitHub
https://github.com/electron/electron/security/advisories/GHSA-jm7p-cc5g-qwxxVendor Advisories for CVE-2026-70597(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| electron | — | 42.0.0-beta.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 18:52 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:03 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 19:50 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-12 00:37 UTCEG score recompute
- 2026-08-07 04:37 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 05:25 UTCEG score recompute
- 2026-08-06 04:25 UTCEG score recompute
- 2026-08-05 16:28 UTCEG score recompute
- 2026-08-05 16:12 UTCEG score recompute
- 2026-08-05 15:26 UTCEG score recompute
- 2026-08-05 15:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-70597?
When was CVE-2026-70597 disclosed?
Is CVE-2026-70597 actively exploited?
What is the CVSS score of CVE-2026-70597?
How do I remediate CVE-2026-70597?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70597
Is Your Infrastructure Affected by CVE-2026-70597?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.