high · 7.4 Patched

Electron: Mitigation for compromised eMudhra intermediate certificates

CVE-2026-115570 · GHSA-jr5w-w6x2-84p9 · published 23 Oct 2026

How serious is it

  • Severity: high, CVSS score 7.4 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-115570?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • electron (npm) >= 45.0.0-alpha.1, < 45.0.0-beta.6
  • electron (npm) >= 44.0.0-alpha.1, < 44.9.1
  • electron (npm) >= 43.0.0-alpha.1, < 43.8.1
  • electron (npm) < 42.11.16

How to check

  1. Run npm ls electron in your project to see the installed version, including copies pulled in by other packages.
  2. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
  3. Or run npx shippable-dev scan localhost:3000 in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. On >= 45.0.0-alpha.1, < 45.0.0-beta.6: Upgrade electron to 45.0.0-beta.6 or later, commit the lockfile and redeploy.
  2. On >= 44.0.0-alpha.1, < 44.9.1: Upgrade electron to 44.9.1 or later, commit the lockfile and redeploy.
  3. On >= 43.0.0-alpha.1, < 43.8.1: Upgrade electron to 43.8.1 or later, commit the lockfile and redeploy.
  4. On < 42.11.16: Upgrade electron to 42.11.16 or later, commit the lockfile and redeploy.
  5. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

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

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities