HighGHSA-jr5w-w6x2-84p9CVE-2026-115570

Electron: Mitigation for compromised eMudhra intermediate certificates

Published 23 Oct 2026 · Updated 23 Oct 2026

Affected packages

electronnpm

Affected: >=45.0.0-alpha.1 <45.0.0-beta.6
Fixed in: 45.0.0-beta.6

Update to the fixed version for your release line, for example:npm install electron@45.0.0-beta.6

electronnpm

Affected: >=44.0.0-alpha.1 <44.9.1
Fixed in: 44.9.1

Update to the fixed version for your release line, for example:npm install electron@44.9.1

electronnpm

Affected: >=43.0.0-alpha.1 <43.8.1
Fixed in: 43.8.1

Update to the fixed version for your release line, for example:npm install electron@43.8.1

electronnpm

Affected: <42.11.16
Fixed in: 42.11.16

Update to the fixed version for your release line, for example:npm install electron@42.11.16

Details

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 [security@electronjs.org](mailto:security@electronjs.org)

Is GHSA-jr5w-w6x2-84p9 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected electron, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.