CVE-2026-70600 — Electron: Cross-origin iframe can position native autofill popup
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3, the native autofill popup could be positioned by a cross-origin iframe outside that iframe's bounds, over the embedding page's UI, enabling clickjacking or spoofing of trusted UI. Apps are only affected if they embed untrusted content in iframes within windows that also display trusted UI. Apps that do not embed untrusted third-party content are not affected. This issue is fixed in versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- 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.
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.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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.
- Identify exposed assets running the affected vendor/product/version combinations (Electron Electron, Electronjs Electron).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Electron | Electron | version < 39.8.8version >= 40.0.0-alpha.1, < 40.9.0version >= 41.0.0-alpha.1, < 41.2.1version >= 42.0.0-alpha.1, < 42.0.0-beta.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Electronjs | Electron |
< 39.8.8≥ 40.0.0 and < 40.9.0≥ 41.0.0 and ≤ 41.2.1version 42.0.0-alpha1version 42.0.0-alpha2version 42.0.0-alpha3version 42.0.0-alpha4version 42.0.0-alpha5 and 3 moreversion 42.0.0-alpha6version 42.0.0-beta1version 42.0.0-beta2 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | Medium | 2.8 | 1.4 | nvd@nist.gov via NIST National Vulnerability Database |
| 3.1 | CVSS 3.1 | Low | 1.6 | 1.4 | security-advisories@github.com via NIST National Vulnerability Database |
| 3.1 | CVSS 3.1 | Low | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.18%
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).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · electron/electron
- SSVC assessment updated
- Record published
- CVSS changed · 4.3
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-102672 Electron: Local race condition in Squirrel.Mac update installation on macOS 2d
- High CVE-2026-102677 Electron: Sandboxed preload code cache can be poisoned by a compromised renderer 16d
- Medium CVE-2026-102673 Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab 16d
- Medium CVE-2026-102674 Electron: Windows opened from a sandboxed top-level document do not inherit its sandbox restrictions 16d
- High CVE-2026-102675 Electron: File and HTTP protocol handlers allow cross-origin reads without corsEnabled 16d
- Critical CVE-2026-102676 Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions 16d
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 fixed version, patch or mitigation documented.
- 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-70600 is "Electron: Cross-origin iframe can position native autofill popup", 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 4.3 describes technical severity. EPSS 0.18% 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.