CVE-2026-102677

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-29) is not newer than that change (2026-10-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-89179 (ENISA EUVD) · GHSA-qmv3-fv6v-rmhq (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 29, 2026

Last Modified

October 8, 2026

Advisory Details (8)

Auto-updated Sep 29, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

electron 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.6
GitHub release Patch Available

electron v43.5.0

Patch available: electron/electron v43.5.0

https://github.com/electron/electron/releases/tag/v43.5.0
GitHub release Patch Available

electron v42.10.0

Patch available: electron/electron v42.10.0

https://github.com/electron/electron/releases/tag/v42.10.0
GitHub commit

commit c38d6fd68756 (electron/electron)

Fix landed in electron/electron commit c38d6fd68756 — awaiting tagged release

https://github.com/electron/electron/commit/c38d6fd68756f04647ea857bdb6a2abec332e217
GitHub commit

commit 25ba8be57c65 (electron/electron)

Fix landed in electron/electron commit 25ba8be57c65 — awaiting tagged release

https://github.com/electron/electron/commit/25ba8be57c65a83d8c14ebb8aa37693df17a04f3
GitHub commit

commit 000453e399bd (electron/electron)

Fix landed in electron/electron commit 000453e399bd — awaiting tagged release

https://github.com/electron/electron/commit/000453e399bd1dee5e86376cdd9ece5fc071e601
GitHub pull request

fix: 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/52480
GitHub advisoryMentions a patch (unverified)

Sandboxed preload code cache can be poisoned by a compromised renderer · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-qmv3-fv6v-rmhq

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmelectron @ 42.10.0 (fixes >= 42.3.3, < 42.10.0)—ghsa
npmelectron @ 43.5.0 (fixes >= 43.0.0-beta.1, < 43.5.0)—ghsa
npmelectron @ 44.0.0-beta.6 (fixes >= 44.0.0-alpha.1, < 44.0.0-beta.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
electron—
  • 42.3.3 up to 42.10.0: fixed in 42.10.0
  • 43.0.0-beta.1 up to 43.5.0: fixed in 43.5.0
  • 44.0.0-alpha.1 up to 44.0.0-beta.6: fixed in 44.0.0-beta.6
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-qmv3-fv6v-rmhq · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-11-01 08:00 UTCEG score recompute
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-31 10:42 UTCEG score recompute
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-25 14:56 UTCEG score recompute
  10. 2026-10-24 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-10-24 15:15 UTCEG score recompute
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-22 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-21 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-20 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-18 05:10 UTCEG score recompute
  19. 2026-10-17 19:49 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-16 16:40 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-10-14 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-10-12 16:40 UTCEG score recompute
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 25 more
  1. 2026-10-11 20:16 UTCEG score recompute
  2. 2026-10-11 18:28 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEG score recompute
  4. 2026-10-11 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-11 00:33 UTCEG score recompute
  6. 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-10-09 22:34 UTCEG score recompute
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-08 20:38 UTCEG score recompute▲ 1.00
  10. 2026-10-08 20:35 UTCNVD updateCVSS v3 → 8.8
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-10-08 11:53 UTCEG score recompute
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-03 15:15 UTCEG score recompute
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-03 02:18 UTCEG score recompute
  17. 2026-10-02 13:18 UTCEG score recompute
  18. 2026-10-02 12:46 UTCEG score recompute
  19. 2026-10-01 21:40 UTCEG score recompute
  20. 2026-10-01 19:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-09-30 19:45 UTCEG score recompute
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-09-29 18:27 UTCEG score recompute
  24. 2026-09-29 17:48 UTCEG score recomputeFirst assessed: 7.8 HIGH
  25. 2026-09-29 17:48 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102677?
CVE-2026-102677 is a high-severity vulnerability; its CVE record was published on September 29, 2026. 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…
When was the CVE record for CVE-2026-102677 published?
The CVE record for CVE-2026-102677 was published on September 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-102677 actively exploited?
CVE-2026-102677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102677?
CVE-2026-102677 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-102677?
A fix for CVE-2026-102677 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102677 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102677

Explore →

Is Your Infrastructure Affected by CVE-2026-102677?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs