CVE-2026-115570

HIGHPre-NVD 7.47.4
EchelonGraph scoreHIGH confidence

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

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-10-23. A secondary CVSS source baseline 7.4; sources differ by 0.0.

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

Also known asEUVD-2026-109120 (ENISA EUVD) · GHSA-jr5w-w6x2-84p9 (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: 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 42.11.16, 43.8.1, 44.9.1, and 45.0.0-beta.6, Electron does not block compromised eMudhra intermediate certificates in Chromium networking, Node.js tls, Node.js https, or Node.js fetch. An attacker who holds a certificate issued through one of these intermediates and can intercept network traffic can impersonate a TLS server to an affected application. This issue is fixed in versions 42.11.16, 43.8.1, 44.9.1, and 45.0.0-beta.6.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
31st
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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

October 23, 2026

Last Modified

October 23, 2026

Advisory Details (10)

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

electron v42.11.16

Patch available: electron/electron v42.11.16

https://github.com/electron/electron/releases/tag/v42.11.16
GitHub commit

commit e02265be96c5 (electron/electron)

Fix landed in electron/electron commit e02265be96c5 — awaiting tagged release

https://github.com/electron/electron/commit/e02265be96c5e13ae43644ef482b718e1e800499
GitHub commit

commit 817c43f92567 (electron/electron)

Fix landed in electron/electron commit 817c43f92567 — awaiting tagged release

https://github.com/electron/electron/commit/817c43f925677eb88034bfba4f0b8dfd28e7ad20
GitHub commit

commit 1d2f13b19854 (electron/electron)

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

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

commit 093583c71be7 (electron/electron)

Fix landed in electron/electron commit 093583c71be7 — awaiting tagged release

https://github.com/electron/electron/commit/093583c71be71c85453e6e225137bf2af755fbcc
GitHub pull request

fix: apply the certificate SPKI blocklist to Node and add entries (43-x-y)

Fix merged in electron/electron PR #55130 on 2026-10-20 — awaiting tagged release

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

fix: apply the certificate SPKI blocklist to Node and add entries (45-x-y)

Fix merged in electron/electron PR #55129 on 2026-10-20 — awaiting tagged release

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

fix: apply the certificate SPKI blocklist to Node and add entries (42-x-y)

Fix merged in electron/electron PR #55128 on 2026-10-20 — awaiting tagged release

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

fix: apply the certificate SPKI blocklist to Node and add entries (44-x-y)

Fix merged in electron/electron PR #55127 on 2026-10-20 — awaiting tagged release

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

Mitigation for compromised eMudhra intermediate certificates · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-jr5w-w6x2-84p9

Vendor Advisories for CVE-2026-115570(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 @ 45.0.0-beta.6 (fixes >= 45.0.0-alpha.1, < 45.0.0-beta.6)—ghsa
npmelectron @ 44.9.1 (fixes >= 44.0.0-alpha.1, < 44.9.1)—ghsa
npmelectron @ 43.8.1 (fixes >= 43.0.0-alpha.1, < 43.8.1)—ghsa
npmelectron @ 42.11.16 (fixes < 42.11.16)—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—
  • 45.0.0-alpha.1 up to 45.0.0-beta.6: fixed in 45.0.0-beta.6
  • 44.0.0-alpha.1 up to 44.9.1: fixed in 44.9.1
  • 43.0.0-alpha.1 up to 43.8.1: fixed in 43.8.1
  • every version up to 42.11.16: fixed in 42.11.16
—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-jr5w-w6x2-84p9 · GitHub severity HIGH · GitHub CVSS 7.4
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-30 16:38 UTCEG score recompute
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-25 14:50 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-23 21:31 UTCEG score recompute
  15. 2026-10-23 21:00 UTCEG score recompute
  16. 2026-10-23 19:32 UTCEG score recompute
  17. 2026-10-23 18:30 UTCEG score recomputeFirst assessed: 7.4 HIGH
  18. 2026-10-23 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-115570?
CVE-2026-115570 is a high-severity vulnerability; its CVE record was published on October 23, 2026. Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 42.11.16, 43.8.1, 44.9.1, and 45.0.0-beta.6, Electron does not block compromised eMudhra intermediate certificates in Chromium networking, Node.js tls, Node.js https, or Node.js fetch.…
When was the CVE record for CVE-2026-115570 published?
The CVE record for CVE-2026-115570 was published on October 23, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-115570 actively exploited?
CVE-2026-115570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115570?
CVE-2026-115570 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-115570?
A fix for CVE-2026-115570 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115570 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-115570

Explore →

Is Your Infrastructure Affected by CVE-2026-115570?

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

Book a Demo →Browse All CVEs