CVE-2026-115570

Electron: Mitigation for compromised eMudhra intermediate certificates

Workarounds

There are no app side workarounds, you must update to a patched version of Electron.

Fixed Versions

• 45.0.0-beta.6
• 44.9.1
• 43.8.1
• 42.11.16

For more information

If you have any questions or comments about this advisory, email us at [email protected]

A set of eMudhra intermediate certificates were compromised and are being blocked by browsers and other TLS clients. This Electron update adds the same block to both Chromium networking and Node.js tls, https and fetch. On earlier versions, an attacker holding a certificate issued through these intermediates and able to intercept network traffic could impersonate a TLS server to an app.

Apps are only affected if they make TLS connections over a network an attacker can intercept. Apps that make no network connections are not affected.

Other software has shipped the same mitigation, including Go (CVE-2026-111943) and Firefox (CVE-2026-113470).

CVE-2026-115570 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (45.0.0-beta.6, 44.9.1, 43.8.1, 42.11.16); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-115570? CVE-2026-115570 is a high-severity security vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-beta.6. It is fixed in 45.0.0-beta.6, 44.9.1, 43.8.1, 42.11.16.
2. How severe is CVE-2026-115570? CVE-2026-115570 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2026-115570? electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-beta.6 is affected.
4. Is there a fix for CVE-2026-115570? Yes. CVE-2026-115570 is fixed in 45.0.0-beta.6, 44.9.1, 43.8.1, 42.11.16. Upgrade to this version or later.
5. Is CVE-2026-115570 exploitable, and should I be worried? Whether CVE-2026-115570 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-115570 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-115570?
   • Upgrade electron to 45.0.0-beta.6 or later
   • Upgrade electron to 44.9.1 or later
   • Upgrade electron to 43.8.1 or later
   • Upgrade electron to 42.11.16 or later

Other vulnerabilities in electron