# Electron: Mitigation for compromised eMudhra intermediate certificates Advisory record · `GHSA-jr5w-w6x2-84p9` - **Identifiers:** `GHSA-jr5w-w6x2-84p9` · `CVE-2026-115570` - **State:** Confirmed - **Severity:** CVSS 7.4 High - **Critical:** No - **Weakness (CWE):** [CWE-299](https://cwe.mitre.org/data/definitions/299.html) - **Tags:** [CWE-299](https://agentprime.io/advisories/tag/cwe-299.md) - **Published:** 23 Oct 2026 - **Updated:** 23 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 23 Oct 2026, 20:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `electron` (npm): affected `>=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`; fixed in `45.0.0-beta.6`, `44.9.1`, `43.8.1`, `42.11.16` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Electron versions before 42.11.16, from 43.0.0-alpha.1 up to 43.8.1, from 44.0.0-alpha.1 up to 44.9.1, and from 45.0.0-alpha.1 up to 45.0.0-beta.6 are affected by a mitigation for compromised eMudhra intermediate certificates. An attacker who holds a certificate issued through those intermediates and can intercept network traffic could impersonate a TLS server to an app, and only apps that make TLS connections over a network an attacker can intercept are affected. Upgrade to 42.11.16, 43.8.1, 44.9.1, or 45.0.0-beta.6 or later, since no app-side workaround exists. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0038, the 31st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jr5w-w6x2-84p9) ## Sources - [GitHub Advisory Database: GHSA-jr5w-w6x2-84p9](https://github.com/advisories/GHSA-jr5w-w6x2-84p9) - [OSV: GHSA-jr5w-w6x2-84p9](https://osv.dev/vulnerability/GHSA-jr5w-w6x2-84p9) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .