Skip to content
Fencer Intel
high 7.4

CVE-2026-115570 json

Electron: Mitigation for compromised eMudhra intermediate certificates

published 17d ago modified 17d ago also EUVD-2026-109120 , GHSA-jr5w-w6x2-84p9

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm electron 42.11.16, 43.8.1, 44.9.1, 45.0.0-beta.6
  • atom electron 42.11.16, 43.8.1, 44.9.1, 45.0.0-beta.6
  • electronjs electron 42.11.16, 43.8.1, 44.9.1, 45.0.0-beta.6
  • mozilla firefox 42.11.16, 43.8.1, 44.9.1, 45.0.0-beta.6

Is CVE-2026-115570 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-115570 updated cvss 7.4

electron: Electron: TLS server impersonation via compromised intermediate certificates

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
17d ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm electron
>=45.0.0-alpha.1, <45.0.0-beta.6
>=44.0.0-alpha.1, <44.9.1
>=43.0.0-alpha.1, <43.8.1
<42.11.16
45.0.0-beta.6
44.9.1
43.8.1
42.11.16

Affected products

  • electron electron

Classification

Weakness
  • CWE-299 Improper Check for Certificate Revocation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.