CVE Intelligence
Medium

CVE-2026-102674 — Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions

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.

Published Sep 29, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.27%
ahead of 17% of scored CVEs · Oct 14, 2026
Affects
Electron
Electron
CVSS base
6.1
Medium · 4 source(s)
Prioritization reference: 8.2 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Npm Electron: fixed in version 41.10.6 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 42.9.2 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 43.4.1 — github.com (GitHub Security Advisories)
  • Npm Electron: fixed in version 44.0.0-beta.5 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Electron Electron, Electronjs Electron, Npm Electron).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Electron Electron version >= 44.0.0-alpha.1, < 44.0.0-beta.5version >= 43.0.0-alpha.1, < 43.4.1version >= 42.0.0-alpha.1, < 42.9.2version < 41.10.6 Vulnerable CVE Program (cve.org) e CISA ADP
Electronjs Electron ≥ 42.0.0 and < 42.9.2version 44.0.0-beta4version 44.0.0-beta3version 44.0.0-beta2version 44.0.0-beta1version 44.0.0-alpha9version 44.0.0-alpha8version 44.0.0-alpha7
and 8 more version 44.0.0-alpha6version 44.0.0-alpha5version 44.0.0-alpha4version 44.0.0-alpha3version 44.0.0-alpha2version 44.0.0-alpha1≥ 43.0.0 and < 43.4.1< 41.10.6
Vulnerable NIST National Vulnerability Database
Npm Electron < 41.10.6≥ 42.0.0-alpha.1 and < 42.9.2≥ 43.0.0-alpha.1 and < 43.4.1≥ 44.0.0-alpha.1 and < 44.0.0-beta.5 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.2 CVSS 3.1 High 2.8 4.7 security-advisories@github.com via NIST National Vulnerability Database
8.2 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.2 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
6.1 CVSS 3.1 Medium 2.8 2.7 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.2 (security-advisories@github.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-266

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · npm/electron
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · electron/electron
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Fix documented
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · electronjs/electron
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 6.1
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Sep 29, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

Elsewhere on this site

Electron
every CVE for this vendor
CWE-266
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-102672 Electron: Local race condition in Squirrel.Mac update installation on macOS 2d
  • CVE-2026-102677 Electron: Sandboxed preload code cache can be poisoned by a compromised renderer 16d
  • CVE-2026-102676 Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions 16d
  • CVE-2026-102673 Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab 16d
  • CVE-2026-70612 Electron: Sandboxed iframes can launch external protocol handlers Aug 5, 2026
  • CVE-2026-70610 Electron: contextBridge object copy honors prototype setters Aug 5, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-102674 is "Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions", rated Medium. It affects Electron (Electron); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.1 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.