CVE-2026-102674

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (17th 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: 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, windows opened from a sandboxed top-level document did not inherit that document's active HTML sandbox restrictions. Untrusted content in a sandboxed top-level document that was permitted to open popups could therefore create a window with the Electron application's full origin instead of the restricted origin intended by the sandbox. Applications that deny such popups with setWindowOpenHandler 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
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 30, 2026

Advisory Details (9)

Auto-updated Sep 29, 2026
Patch available. Sources: github, github_commit, github_release.
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 e9c4d3cbe912 (electron/electron)

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

https://github.com/electron/electron/commit/e9c4d3cbe912e18d7c63af78e63e98ae7a48cd3a
github_commit

commit 6594d5a5b074 (electron/electron)

Fix landed in electron/electron commit 6594d5a5b074 — awaiting tagged release

https://github.com/electron/electron/commit/6594d5a5b074cf501da084dc7908d3df0d68a886
github_commit

commit 3ecf3e74f4be (electron/electron)

Fix landed in electron/electron commit 3ecf3e74f4be — awaiting tagged release

https://github.com/electron/electron/commit/3ecf3e74f4be6e2360644679b0b4698742be0e1d
github_commit

commit 29fc130569f9 (electron/electron)

Fix landed in electron/electron commit 29fc130569f9 — awaiting tagged release

https://github.com/electron/electron/commit/29fc130569f970e91e355383821a4af0f25724a2
github Patch Available

Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions · Advisory · electron/electron · GitHub

https://github.com/electron/electron/security/advisories/GHSA-gr2m-v5gq-v685

Vendor Advisories for CVE-2026-102674(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)
PackageVulnerable rangeFixed inDependents
electron—41.10.6—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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.

  1. 2026-10-03 23:33 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 01:55 UTCEG score recompute
  4. 2026-10-02 04:16 UTCEG score recompute
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-09-30 16:16 UTCEG score recompute
  7. 2026-09-30 15:02 UTCEPSS rescore
  8. 2026-09-29 18:31 UTCEG score recompute
  9. 2026-09-29 17:29 UTCEG score recompute
  10. 2026-09-29 16:54 UTCEG score recompute
  11. 2026-09-29 16:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102674?
CVE-2026-102674 is a high vulnerability 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, windows opened from a sandboxed top-level document did not inherit that document's active HTML sandbox restrictions. Untrusted content in a…
When was CVE-2026-102674 disclosed?
CVE-2026-102674 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102674 actively exploited?
CVE-2026-102674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102674?
CVE-2026-102674 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102674?
A fix for CVE-2026-102674 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102674 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-102674

Explore →

Is Your Infrastructure Affected by CVE-2026-102674?

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