Electron: Mitigation for compromised eMudhra intermediate certificatesGHSA-jr5w-w6x2-84p9
HIGHFix: electron/electron#55127GHSA-jr5w-w6x2-84p9 is a high-severity (CVSS 7.4) CWE-299 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jr5w-w6x2-84p9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jr5w-w6x2-84p9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
electron📦electron📦electron📦electronReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.644.9.143.8.142.11.16
For more information
If you have any questions or comments about this advisory, email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | electron | ≥ 45.0.0-alpha.1&&< 45.0.0-beta.6 | 45.0.0-beta.6npm install electron@45.0.0-beta.6 |
| 📦npm | electron | ≥ 44.0.0-alpha.1&&< 44.9.1 | 44.9.1npm install electron@44.9.1 |
| 📦npm | electron | ≥ 43.0.0-alpha.1&&< 43.8.1 | 43.8.1npm install electron@43.8.1 |
| 📦npm | electron | all versions | 42.11.16npm install electron@42.11.16 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 45.0.0-beta.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jr5w-w6x2-84p9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-jr5w-w6x2-84p9 in your dependencies?
Find it across npm, including transitive dependencies.