CVE-2026-70597

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100CISA SSVC

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 computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 0a6291a97d21 (electron/electron)

Fix landed in electron/electron commit 0a6291a97d21 — awaiting tagged release

https://github.com/electron/electron/commit/0a6291a97d210db3733689e70a51f5711e38ed35
github Patch Available

Parent process code-sign check is spoofable · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-jm7p-cc5g-qwxx

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
electron—
  • every version up to 39.8.8: fixed in 39.8.8
  • 40.0.0-alpha.1 up to 40.9.1: fixed in 40.9.1
  • 41.0.0-alpha.1 up to 41.2.1: fixed in 41.2.1
  • 42.0.0-alpha.1 up to 42.0.0-beta.3: fixed in 42.0.0-beta.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 06:00 UTCEG score recompute
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-02 09:55 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-10-01 02:18 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 06:15 UTCEG score recompute
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 17:42 UTCEG score recompute
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-25 04:31 UTCEG score recompute
  15. 2026-09-23 00:42 UTCEG score recompute
  16. 2026-09-22 01:30 UTCEG score recompute
  17. 2026-09-21 21:09 UTCEPSS rescore
  18. 2026-09-20 03:15 UTCEG score recompute
  19. 2026-09-19 03:25 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 03:03 UTCEG score recompute
  22. 2026-09-17 03:51 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 03:12 UTCEG score recompute
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 47 more
  1. 2026-09-13 00:08 UTCEG score recompute
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-12 00:55 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 01:42 UTCEG score recompute
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-10 02:29 UTCEG score recompute
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 18:17 UTCEG score recompute
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 07:58 UTCEG score recompute
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-05 08:45 UTCEG score recompute
  15. 2026-09-04 09:32 UTCEG score recompute
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-01 22:11 UTCEG score recompute
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 20:35 UTCEG score recompute
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-29 21:23 UTCEG score recompute
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-28 13:57 UTCEG score recompute
  25. 2026-08-27 12:43 UTCEG score recompute
  26. 2026-08-26 14:47 UTCEPSS rescore
  27. 2026-08-24 14:56 UTCEG score recompute
  28. 2026-08-23 15:43 UTCEG score recompute
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-21 17:16 UTCEG score recompute
  31. 2026-08-20 22:56 UTCEPSS rescore
  32. 2026-08-19 18:52 UTCEG score recompute
  33. 2026-08-19 17:04 UTCEPSS rescore
  34. 2026-08-18 19:03 UTCEG score recompute
  35. 2026-08-18 13:49 UTCEPSS rescore
  36. 2026-08-18 13:49 UTCEPSS rescore
  37. 2026-08-17 19:50 UTCEG score recompute
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-12 00:37 UTCEG score recompute
  40. 2026-08-07 04:37 UTCEG score recompute
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-06 05:25 UTCEG score recompute
  43. 2026-08-06 04:25 UTCEG score recompute
  44. 2026-08-05 16:28 UTCEG score recompute
  45. 2026-08-05 16:12 UTCEG score recompute
  46. 2026-08-05 15:26 UTCEG score recompute
  47. 2026-08-05 15:25 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-70597?
CVE-2026-70597 is a medium vulnerability published on August 5, 2026. 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…
When was CVE-2026-70597 disclosed?
CVE-2026-70597 was first published on August 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70597 actively exploited?
CVE-2026-70597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70597?
CVE-2026-70597 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70597?
A fix for CVE-2026-70597 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70597 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70597

Explore →

Is Your Infrastructure Affected by CVE-2026-70597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs