CVE Intelligence
Medium Access control

CVE-2026-34780 — Electron: Context Isolation bypass via contextBridge VideoFrame transfer

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. From versions 39.0.0-alpha.1 to before 39.8.0, 40.0.0-alpha.1 to before 40.7.0, and 41.0.0-alpha.1 to before 41.0.0-beta.8, apps that pass VideoFrame objects (from the WebCodecs API) across the contextBridge are vulnerable to a context isolation bypass. An attacker who can execute JavaScript in the main world (for example, via XSS) can use a bridged VideoFrame to gain access to the isolated world, including any Node.js APIs exposed to the preload script. Apps are only affected if a preload script returns, resolves, or passes a VideoFrame object to the main world via contextBridge.exposeInMainWorld(). Apps that do not bridge VideoFrame objects are not affected. This issue has been patched in versions 39.8.0, 40.7.0, and 41.0.0-beta.8.

Published Apr 3, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · 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.4% (30-day exploitation probability)+6
  • 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.45%
ahead of 37% of scored CVEs · Oct 14, 2026
Affects
Electron
Electron
CVSS base
6.1
Medium · 4 source(s)
Prioritization reference: 8.4 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
Total
partial · total control of the vulnerable component

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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Electron Electron, Electronjs Electron).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Electron Electron version >= 41.0.0-alpha.1, < 41.0.0-beta.8version >= 40.0.0-alpha.1, < 40.7.0version >= 39.0.0-alpha.1, < 39.8.0 Vulnerable CVE Program (cve.org) e CISA ADP
Electronjs Electron version 41.0.0-beta2version 41.0.0-beta7version 41.0.0-beta6version 41.0.0-beta5version 41.0.0-beta4version 41.0.0-beta3≥ 39.0.0 and < 39.8.0version 41.0.0-beta1
and 7 more version 41.0.0-alpha6version 41.0.0-alpha5version 41.0.0-alpha4version 41.0.0-alpha3version 41.0.0-alpha2version 41.0.0-alpha1≥ 40.0.0 and < 40.7.0
Vulnerable NIST National Vulnerability Database

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.4 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
8.3 CVSS 3.1 High 1.6 6.0 security-advisories@github.com via NIST National Vulnerability Database
8.0 CVSS 3.1 High 1.3 6.0 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
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.4 (GitHub_M via CVE Program (cve.org) e CISA ADP) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-668 · Exposure of Resource to Wrong Sphere

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.45%

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).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · electron/electron
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Apr 3, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Electron
every CVE for this vendor
Access control
same class
CWE-668
other pages naming this weakness

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
  • Critical CVE-2026-102676 Electron: <webview> can enable Node.js integration in Web Workers despite embedder restrictions 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
  • Medium CVE-2026-70612 Electron: Sandboxed iframes can launch external protocol handlers 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 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-34780 is "Electron: Context Isolation bypass via contextBridge VideoFrame transfer", 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.45% 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.