CVE-2026-70611

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.9 from GitHub Security Advisory (severity: MODERATE) published 2026-08-05. A secondary CVSS source baseline 6.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-53545 (ENISA EUVD) · GHSA-f2r8-jv7c-xqmp (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.9Exploit: 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.9, 40.9.2, 41.2.1, and 42.0.0-beta.3, the DevTools reveal in file manager action could launch the target file rather than reveal it. An attacker with a separate means of running script inside the DevTools frontend, such as a malicious DevTools extension, could use showItemInFolder handling to execute native code outside the sandbox when DevTools is opened for windows exposed to untrusted content or untrusted DevTools extensions. This issue is fixed in 39.8.9, 40.9.2, 41.2.1, and 42.0.0-beta.3.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

October 8, 2026

Advisory Details (10)

Auto-updated Aug 5, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

electron v39.8.9

Patch available: electron/electron v39.8.9

https://github.com/electron/electron/releases/tag/v39.8.9
GitHub commit

commit 7a1eb7e55859 (electron/electron)

Fix landed in electron/electron commit 7a1eb7e55859 — awaiting tagged release

https://github.com/electron/electron/commit/7a1eb7e5585991b3726cedb890a6244f327f43de
GitHub commit

commit 27bf1cae9274 (electron/electron)

Fix landed in electron/electron commit 27bf1cae9274 — awaiting tagged release

https://github.com/electron/electron/commit/27bf1cae9274d5025684c7268496f435b7e06b44
GitHub commit

commit 1b8a298d629d (electron/electron)

Fix landed in electron/electron commit 1b8a298d629d — awaiting tagged release

https://github.com/electron/electron/commit/1b8a298d629d5a642c816ea5f7505359de17b771
GitHub commit

commit 10fb5b39c528 (electron/electron)

Fix landed in electron/electron commit 10fb5b39c528 — awaiting tagged release

https://github.com/electron/electron/commit/10fb5b39c5287f70c4bbcab4c24197f3871ec322
GitHub pull request

fix: use ShowItemInFolder for devtools showItemInFolder embedder message

Fix merged in electron/electron PR #51115 on 2026-04-17 — awaiting tagged release

https://github.com/electron/electron/pull/51115
GitHub pull request

fix: use ShowItemInFolder for devtools showItemInFolder embedder message

Fix merged in electron/electron PR #51114 on 2026-04-17 — awaiting tagged release

https://github.com/electron/electron/pull/51114
GitHub pull request

fix: use ShowItemInFolder for devtools showItemInFolder embedder message

Fix merged in electron/electron PR #50938 on 2026-04-11 — awaiting tagged release

https://github.com/electron/electron/pull/50938
GitHub pull request

fix: use ShowItemInFolder for devtools showItemInFolder embedder message

Fix merged in electron/electron PR #50937 on 2026-04-12 — awaiting tagged release

https://github.com/electron/electron/pull/50937
GitHub advisoryMentions a patch (unverified)

DevTools embedder handler executes arbitrary files via shell open · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-f2r8-jv7c-xqmp

Vendor Advisories for CVE-2026-70611(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmelectron @ 39.8.9 (fixes < 39.8.9)—ghsa
npmelectron @ 40.9.2 (fixes >= 40.0.0-alpha.1, < 40.9.2)—ghsa
npmelectron @ 41.2.1 (fixes >= 41.0.0-alpha.1, < 41.2.1)—ghsa
npmelectron @ 42.0.0-beta.3 (fixes >= 42.0.0-alpha.1, < 42.0.0-beta.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
electron—
  • every version up to 39.8.9: fixed in 39.8.9
  • 40.0.0-alpha.1 up to 40.9.2: fixed in 40.9.2
  • 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 / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 142 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-f2r8-jv7c-xqmp · GitHub severity MODERATE · GitHub CVSS 6.9
  3. 2026-11-01 07:40 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-30 07:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-25 14:08 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 19:30 UTCEG score recompute
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-18 03:18 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 75 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-12 15:43 UTCEG score recompute
  4. 2026-10-11 19:29 UTCEG score recompute
  5. 2026-10-11 16:44 UTCEG score recompute
  6. 2026-10-11 14:04 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-08 14:09 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-06 23:36 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-05 19:33 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-04 05:58 UTCEG score recompute
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-02 09:52 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-01 02:15 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-29 06:13 UTCEG score recompute
  26. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-27 17:39 UTCEG score recompute
  28. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-25 04:30 UTCEG score recompute
  31. 2026-09-23 22:01 UTCEG score recompute
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-09-22 23:58 UTCEG score recompute
  34. 2026-09-22 01:24 UTCEG score recompute
  35. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  36. 2026-09-20 21:24 UTCEG score recompute
  37. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-09-19 23:15 UTCEG score recompute
  39. 2026-09-19 01:12 UTCEG score recompute
  40. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-09-18 03:01 UTCEG score recompute
  42. 2026-09-17 04:57 UTCEG score recompute
  43. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-09-16 06:53 UTCEG score recompute
  45. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-09-15 08:49 UTCEG score recompute
  47. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  48. 2026-09-14 10:38 UTCEG score recompute
  49. 2026-09-13 12:27 UTCEG score recompute
  50. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-09-11 16:19 UTCEG score recompute
  52. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  53. 2026-09-10 17:53 UTCEG score recompute
  54. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-09-09 19:12 UTCEG score recompute
  56. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-09-07 18:12 UTCEG score recompute
  58. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-09-06 05:37 UTCEG score recompute
  61. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-09-05 07:33 UTCEG score recompute
  63. 2026-09-04 09:29 UTCEG score recompute
  64. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-09-03 06:44 UTCEG score recompute
  66. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  67. 2026-09-01 20:50 UTCEG score recompute
  68. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  69. 2026-08-30 19:24 UTCEG score recompute
  70. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  71. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  72. 2026-08-29 21:20 UTCEG score recompute
  73. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  74. 2026-08-28 12:32 UTCEG score recompute
  75. 2026-08-27 09:04 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-70611?
CVE-2026-70611 is a medium-severity vulnerability; its CVE record was published on August 5, 2026. Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.9, 40.9.2, 41.2.1, and 42.0.0-beta.3, the DevTools reveal in file manager action could launch the target file rather than reveal it. An attacker with a separate means of running…
When was the CVE record for CVE-2026-70611 published?
The CVE record for CVE-2026-70611 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-70611 actively exploited?
CVE-2026-70611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70611?
CVE-2026-70611 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70611?
A fix for CVE-2026-70611 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70611 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-70611

Explore →

Is Your Infrastructure Affected by CVE-2026-70611?

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