Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From 42.3.3 until 42.10.0, 43.5.0, and 44.0.0-beta.6, Electron's sandboxed preload code cache did not verify that a cached entry matched the preload it was served for. A compromised renderer could write attacker-controlled cache data and cause Electron to reuse it for a later load, executing the renderer's code in the more privileged preload context. The issue affects applications that load untrusted content. This issue is fixed in versions 42.10.0, 43.5.0, and 44.0.0-beta.6.
CVE-2026-102677
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 29, 2026
Last Modified
October 2, 2026
Advisory Details (8)
Auto-updated Sep 29, 2026electron v44.0.0-beta.6
Patch available: electron/electron v44.0.0-beta.6 (pre-release)
https://github.com/electron/electron/releases/tag/v44.0.0-beta.6electron v43.5.0
Patch available: electron/electron v43.5.0
https://github.com/electron/electron/releases/tag/v43.5.0electron v42.10.0
Patch available: electron/electron v42.10.0
https://github.com/electron/electron/releases/tag/v42.10.0commit c38d6fd68756 (electron/electron)
Fix landed in electron/electron commit c38d6fd68756 — awaiting tagged release
https://github.com/electron/electron/commit/c38d6fd68756f04647ea857bdb6a2abec332e217commit 25ba8be57c65 (electron/electron)
Fix landed in electron/electron commit 25ba8be57c65 — awaiting tagged release
https://github.com/electron/electron/commit/25ba8be57c65a83d8c14ebb8aa37693df17a04f3commit 000453e399bd (electron/electron)
Fix landed in electron/electron commit 000453e399bd — awaiting tagged release
https://github.com/electron/electron/commit/000453e399bd1dee5e86376cdd9ece5fc071e601fix: key sandboxed preload code cache entries by consuming site
Fix merged in electron/electron PR #52480 on 2026-08-05 — awaiting tagged release
https://github.com/electron/electron/pull/52480Sandboxed preload code cache can be poisoned by a compromised renderer · Advisory · electron/electron · GitHub
https://github.com/electron/electron/security/advisories/GHSA-qmv3-fv6v-rmhqVendor Advisories for CVE-2026-102677(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| electron | — | 42.10.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-03 15:15 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 02:18 UTCEG score recompute
- 2026-10-02 13:18 UTCEG score recompute
- 2026-10-02 12:46 UTCEG score recompute
- 2026-10-01 21:40 UTCEG score recompute
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 19:45 UTCEG score recompute
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 18:27 UTCEG score recompute
- 2026-09-29 17:48 UTCEG score recompute
- 2026-09-29 17:48 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownnpm:electron
- CVE-2026-34775EG 9.8CRITICAL
- CVE-2017-16151EG 9.8CRITICAL
- CVE-2022-4135EG 9.6 KEVEPSS p98CRITICAL
- CVE-2026-54257EG 9.3CRITICAL
- CVE-2023-5217NVD 8.8EG 9.0 KEVEPSS p99CRITICAL
- CVE-2023-4863NVD 8.8EG 9.0 KEVEPSS p100CRITICAL
- CVE-2018-1000006NVD 8.8EG 9.0EPSS p100CRITICAL
- CVE-2026-34765EG 8.8HIGH
- CVE-2026-34772EG 8.8HIGH
- CVE-2026-34771EG 8.8HIGH
Frequently asked(5)
What is CVE-2026-102677?
When was CVE-2026-102677 disclosed?
Is CVE-2026-102677 actively exploited?
What is the CVSS score of CVE-2026-102677?
How do I remediate CVE-2026-102677?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102677
Is Your Infrastructure Affected by CVE-2026-102677?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.