CVE-2026-102676

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.3 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-15), 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-89095 (ENISA EUVD) · GHSA-9qh4-3jw8-366w (GitHub Security Advisories)Source: ENISA EUVD

9.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.5%CVSS: 9.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. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, an Electron guest could enable nodeIntegrationInWorker for its Web Workers even when the unsandboxed embedder had Node.js integration disabled, allowing untrusted guest content to create a Node-enabled worker with more privilege than the embedder granted. Applications that do not enable the tag or that keep the embedder sandboxed are not affected. This issue is fixed in versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
41st
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 15, 2026

Advisory Details (9)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

<webview> can enable Node.js integration in Web Workers despite embedder restrictions · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-9qh4-3jw8-366w
GitHub release Patch Available

electron v44.0.0-beta.5

Patch available: electron/electron v44.0.0-beta.5 (pre-release)

https://github.com/electron/electron/releases/tag/v44.0.0-beta.5
GitHub release Patch Available

electron v43.4.1

Patch available: electron/electron v43.4.1

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

electron v42.9.2

Patch available: electron/electron v42.9.2

https://github.com/electron/electron/releases/tag/v42.9.2
GitHub release Patch Available

electron v41.10.6

Patch available: electron/electron v41.10.6

https://github.com/electron/electron/releases/tag/v41.10.6
GitHub commit

commit cd34f335c866 (electron/electron)

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

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

commit b3ae0aab5cf8 (electron/electron)

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

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

commit 9a675aef8822 (electron/electron)

Fix landed in electron/electron commit 9a675aef8822 — awaiting tagged release

https://github.com/electron/electron/commit/9a675aef8822bae4088567822969f900b3a37671
GitHub commit

commit 6462a2e1dc4e (electron/electron)

Fix landed in electron/electron commit 6462a2e1dc4e — awaiting tagged release

https://github.com/electron/electron/commit/6462a2e1dc4e6adffd3b7d9b9be1474c45dcbbe2

Vendor Advisories for CVE-2026-102676(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmelectron @ 41.10.6 (fixes < 41.10.6)—ghsa
npmelectron @ 42.9.2 (fixes >= 42.0.0-alpha.1, < 42.9.2)—ghsa
npmelectron @ 43.4.1 (fixes >= 43.0.0-alpha.1, < 43.4.1)—ghsa
npmelectron @ 44.0.0-beta.5 (fixes >= 44.0.0-alpha.1, < 44.0.0-beta.5)—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—
  • every version up to 41.10.6: fixed in 41.10.6
  • 42.0.0-alpha.1 up to 42.9.2: fixed in 42.9.2
  • 43.0.0-alpha.1 up to 43.4.1: fixed in 43.4.1
  • 44.0.0-alpha.1 up to 44.0.0-beta.5: fixed in 44.0.0-beta.5
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 66× 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-02 02:49 UTCEG score recompute
  2. 2026-11-02 02:49 UTCGHSA enrichmentGHSA-9qh4-3jw8-366w · GitHub severity HIGH · GitHub CVSS 8.3
  3. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-9qh4-3jw8-366w · GitHub severity HIGH · GitHub CVSS 8.3
  5. 2026-11-01 08:00 UTCEG score recompute
  6. 2026-11-01 03:43 UTCEG score recompute
  7. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-31 04:37 UTCEG score recompute
  9. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-30 05:31 UTCEG score recompute
  11. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-29 06:25 UTCEG score recompute
  13. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-28 07:19 UTCEG score recompute
  15. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-27 08:14 UTCEG score recompute
  17. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-26 06:51 UTCEG score recompute
  19. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-10-25 14:56 UTCEG score recompute
  21. 2026-10-25 07:38 UTCEG score recompute
  22. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-24 08:32 UTCEG score recompute
  24. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-23 09:26 UTCEG score recompute
Show 51 more
  1. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-22 10:18 UTCEG score recompute
  3. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-21 11:08 UTCEG score recompute
  5. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-20 12:03 UTCEG score recompute
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-19 12:54 UTCEG score recompute
  9. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-18 05:10 UTCEG score recompute
  11. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-17 12:24 UTCEG score recompute
  13. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-16 13:16 UTCEG score recompute
  15. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-15 14:07 UTCEG score recompute▲ 1.50
  17. 2026-10-15 14:04 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  18. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-10-12 16:40 UTCEG score recompute
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-10-11 20:16 UTCEG score recompute
  23. 2026-10-11 17:12 UTCEG score recompute
  24. 2026-10-11 15:02 UTCEG score recompute
  25. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  26. 2026-10-11 04:08 UTCEG score recompute
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  28. 2026-10-10 02:02 UTCEG score recompute
  29. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  30. 2026-10-08 23:55 UTCEG score recompute
  31. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  32. 2026-10-08 10:53 UTCEG score recompute
  33. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  34. 2026-10-06 19:23 UTCEG score recompute
  35. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  36. 2026-10-06 06:21 UTCEG score recompute
  37. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  38. 2026-10-05 04:16 UTCEG score recompute
  39. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  40. 2026-10-04 02:06 UTCEG score recompute
  41. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  42. 2026-10-02 23:58 UTCEG score recompute
  43. 2026-10-01 21:53 UTCEG score recompute
  44. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  45. 2026-09-30 19:45 UTCEG score recompute
  46. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  47. 2026-09-29 20:29 UTCEG score recompute
  48. 2026-09-29 20:01 UTCEG score recompute
  49. 2026-09-29 17:29 UTCEG score recompute
  50. 2026-09-29 17:03 UTCEG score recomputeFirst assessed: 8.3 HIGH
  51. 2026-09-29 17:03 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102676?
CVE-2026-102676 is a critical-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. Prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5, an Electron <webview> guest could enable nodeIntegrationInWorker for its Web Workers even when the unsandboxed embedder had Node.js…
When was the CVE record for CVE-2026-102676 published?
The CVE record for CVE-2026-102676 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-102676 actively exploited?
CVE-2026-102676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102676?
CVE-2026-102676 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-102676?
A fix for CVE-2026-102676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102676 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-102676

Explore →

Is Your Infrastructure Affected by CVE-2026-102676?

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

Book a Demo →Browse All CVEs