KEVWire

Security intelligence, with context.

Response snapshot Oct 26, 2026, 23:07 UTC

Back to the wire
Permalink
VulnerabilityCVE-2026-115570

Electron: Mitigation for compromised eMudhra intermediate certificates

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

At a glance

Exploited
Not known
Severity
7.4 High (CVSS 3.1)
Chance of exploitation
0.4% in the next 30 days
Sources
2 independent sources

What to do

GitHub lists first patched versions: electron: 45.0.0-beta.6; electron: 44.9.1; electron: 43.8.1; electron: 42.11.16. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-jr5w-w6x2-84p9 (opens a new tab)

What happened

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

Continue reading

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

Affected package ranges reported by GitHub: electron: >= 45.0.0-alpha.1, < 45.0.0-beta.6 electron: >= 44.0.0-alpha.1, < 44.9.1 electron: >= 43.0.0-alpha.1, < 43.8.1 electron: < 42.11.16

Scores and how they were measured

CVSS base severity

7.4

Version 3.1As of

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

0.4%

Scored Percentile 31.5%

Model and measurement source (opens a new tab)

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-jr5w-w6x2-84p9 (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-jr5w-w6x2-84p9, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

  3. Primary source

    NVD CVE-2026-115570 (opens a new tab)

    NVD record: description, CVSS (the CNA score is preferred), affected products, and publication date. Not evidence of exploitation.

    Published Checked

  4. Primary source

    NVD CVE API 2.0 (opens a new tab)

    The NVD API page that supplied this CVE record.

    Published Date not suppliedChecked

  5. Primary source

    FIRST measured EPSS score (opens a new tab)

    Measured EPSS probability and percentile for CVE-2026-115570, scored 2026-10-26. This is a model estimate, not proof of exposure.

    Published Checked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 23). Electron: Mitigation for compromised eMudhra intermediate certificates (CVE-2026-115570). https://kevwire.com/record/CVE-2026-115570

MLA

"Electron: Mitigation for compromised eMudhra intermediate certificates (CVE-2026-115570)." KEVWire, 23 Oct. 2026, kevwire.com/record/CVE-2026-115570.

Chicago

KEVWire. "Electron: Mitigation for compromised eMudhra intermediate certificates (CVE-2026-115570)." Last modified October 23, 2026. https://kevwire.com/record/CVE-2026-115570.

Evidence summary (plain text)

Electron: Mitigation for compromised eMudhra intermediate certificates (Oct 23, 2026).
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.
CVSS 7.4 (version 3.1; evidence as of Oct 23, 2026; https://nvd.nist.gov/vuln/detail/CVE-2026-115570).
EPSS 0.4% for the following 30 days, scored Oct 26, 2026 (https://api.first.org/data/v1/epss?cve=CVE-2026-115570&date=2026-10-26).
Sources:
GitHub-reviewed advisory GHSA-jr5w-w6x2-84p9: https://github.com/advisories/GHSA-jr5w-w6x2-84p9
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
NVD CVE-2026-115570: https://nvd.nist.gov/vuln/detail/CVE-2026-115570
NVD CVE API 2.0: https://services.nvd.nist.gov/rest/json/cves/2.0?pubStartDate=2026-10-12T13:35:55.142Z&pubEndDate=2026-10-26T13:35:55.142Z&resultsPerPage=500&startIndex=9000
FIRST measured EPSS score: https://api.first.org/data/v1/epss?cve=CVE-2026-115570&date=2026-10-26
Record ID: CVE-2026-115570.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 26, 2026, 19:40 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail