NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-115570: Electron: Mitigation for compromised eMudhra intermediate certificates

highCVSS 3.1 7.4GHSA-jr5w-w6x2-84p9

Older Electron releases still trust a set of compromised eMudhra intermediate certificates. An attacker with a certificate issued through them, who can intercept network traffic, could impersonate a TLS server to an Electron app. Fixed in 45.0.0-beta.6, 44.9.1, 43.8.1 and 42.11.16. There is no app-side workaround.

Published Oct 23, 2026 · Analysis Nov 2, 2026

What an attacker can do

Browsers and other TLS clients now block these intermediates. Electron has two TLS stacks: Chromium networking and Node.js (tls, https and fetch). The patched releases add the same block to both. On earlier versions, a certificate that chains to a compromised eMudhra intermediate is accepted as valid for any host name.

To use this, an attacker needs two things: such a certificate, and a position to intercept the victim's traffic, for example on shared Wi-Fi or a compromised network hop. The CVSS 3.1 vector reflects that with network attack, high complexity, no user interaction, and high confidentiality and integrity impact.

The attacker can then read and change the app's HTTPS traffic: API tokens, session cookies, update checks and any data sent to the backend. Apps that never open a network connection are not affected. Go (CVE-2026-111943) and Firefox (CVE-2026-113470) shipped the same mitigation, per the advisory.

Who is affected

npm package electron: 45.0.0-alpha.1 up to but not including 45.0.0-beta.6, 44.0.0-alpha.1 up to but not including 44.9.1, 43.0.0-alpha.1 up to but not including 43.8.1, and everything before 42.11.16. The issue matters for apps that make TLS connections over networks an attacker can intercept.

npm ls electron

For a built app, check the Electron version it bundles with process.versions.electron.

electron

Ecosystem
npm
Affected
>= 45.0.0-alpha.1, < 45.0.0-beta.6
Fixed in
45.0.0-beta.6
Check
npm ls electron

electron

Ecosystem
npm
Affected
>= 44.0.0-alpha.1, < 44.9.1
Fixed in
44.9.1
Check
npm ls electron

electron

Ecosystem
npm
Affected
>= 43.0.0-alpha.1, < 43.8.1
Fixed in
43.8.1
Check
npm ls electron

electron

Ecosystem
npm
Affected
< 42.11.16
Fixed in
42.11.16
Check
npm ls electron

How to fix it

Upgrade Electron to a patched release on your line: 45.0.0-beta.6, 44.9.1, 43.8.1 or 42.11.16, then rebuild and ship the app.

npm install [email protected]

The advisory says no app-side workaround exists, so users of an old shipped build stay exposed until you release an update.

How to tell if you were hit

A successful attack leaves no marker in the app. Look at the Electron version in each shipped build, and track which users still run old builds. If you log TLS failures, note that patched apps reject these certificates, which can show up as new certificate errors for hosts that used to work.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

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).

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]](mailto:[email protected])

Credited to MarshallOfSound.

Questions

Do I need to change my app code?

No. The advisory says there is no app-side workaround. The block is part of the patched Electron release, so you update Electron and rebuild.

Is my offline Electron app affected?

The advisory says apps that make no network connections are not affected. The risk is TLS traffic over a network an attacker can intercept.

Is CVE-2026-115570 exploited in the wild?

No source here reports exploitation, and it is not in CISA's KEV catalog.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More npm vulnerabilities

All npm entries