# Electron: Sandboxed preload code cache can be poisoned by a compromised renderer Advisory record · `GHSA-qmv3-fv6v-rmhq` - **Identifiers:** `GHSA-qmv3-fv6v-rmhq` · `CVE-2026-102677` - **State:** Confirmed - **Severity:** CVSS 7.8 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-345](https://cwe.mitre.org/data/definitions/345.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md) - **Published:** 29 Sept 2026 - **Updated:** 29 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 29 Sept 2026, 18:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `electron` (npm): affected `>=42.3.3, <42.10.0 || >=43.0.0-beta.1, <43.5.0 || >=44.0.0-alpha.1, <44.0.0-beta.6`; fixed in `42.10.0`, `43.5.0`, `44.0.0-beta.6` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Electron versions from 42.3.3 before 42.10.0, from 43.0.0-beta.1 before 43.5.0, and from 44.0.0-alpha.1 before 44.0.0-beta.6 are affected. The cache for sandboxed preload scripts did not check that a cached entry matched the preload it was served for, so a compromised renderer could run its own code in the preload context on a later load. Apps that load untrusted content are affected, and there are no app-side workarounds; upgrade to 42.10.0, 43.5.0, or 44.0.0-beta.6. 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.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0010, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:34 UTC: First seen by agentprime - 31 Oct 2026, 13:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qmv3-fv6v-rmhq) ## Sources - [GitHub Advisory Database: GHSA-qmv3-fv6v-rmhq](https://github.com/advisories/GHSA-qmv3-fv6v-rmhq) - [OSV: GHSA-qmv3-fv6v-rmhq](https://osv.dev/vulnerability/GHSA-qmv3-fv6v-rmhq) - - - - - - - - - - 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: .