cve.bz

CVE-2026-115570 electron electron

7.4 highEPSS 0.4%Fix available

High (7.4) in electron electron. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in electron 42.11.16, 43.8.1, 44.9.1.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-299 Improper Check for Certificate Revocation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • electron (npm): fixed in 45.0.0-beta.6, 44.9.1, 43.8.1, 42.11.16

Ask an AI about this CVE

Show the promptExplain CVE-2026-115570 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115570?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115570?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115570 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
electron>= 45.0.0-alpha.1, < 45.0.0-beta.6
electron>= 44.0.0-alpha.1, < 44.9.1
electron>= 43.0.0-alpha.1, < 43.8.1
electron< 42.11.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jr5w-w6x2-84p9npmelectron>=45.0.0-alpha.1 <45.0.0-beta.645.0.0-beta.6
GHSA-jr5w-w6x2-84p9npmelectron>=44.0.0-alpha.1 <44.9.144.9.1
GHSA-jr5w-w6x2-84p9npmelectron>=43.0.0-alpha.1 <43.8.143.8.1
GHSA-jr5w-w6x2-84p9npmelectron<42.11.1642.11.16

References

Check your stackJSON