Electron: Context Isolation bypass via contextBridge VideoFrame transfer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-34780: 0.33% estimated exploitation activity in the next 30 days; percentile 26.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Workarounds Do not pass VideoFrame objects across contextBridge. If an app needs to transfer video frame data, serialize it to an ArrayBuffer or ImageBitmap before bridging. Fixed Versions 41.0.0-beta.8 40.7.0 39.8.0 For more information If there are any questions or comments about this advisory, please email security@electronjs.org

Published by the source

3 Apr 2026, 02:46 UTC

Last modified by the source

6 Apr 2026, 23:19 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jfqg-hf23-qpw2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jfqg-hf23-qpw2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34780

Advisory: Electron: Context Isolation bypass via contextBridge VideoFrame transfer
IDs: CVE-2026-34780, GHSA-jfqg-hf23-qpw2
Record: https://patchnext.com/advisories/cve-2026-34780 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 41.0.0-beta.8, 40.7.0, 39.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected >= 39.0.0-alpha.1, < 39.8.0; >= 40.0.0-alpha.1, < 40.7.0; >= 41.0.0-alpha.1, < 41.0.0-beta.8; fixed in 41.0.0-beta.8, 39.8.0, 40.7.0

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jfqg-hf23-qpw2 (OSV record GHSA-jfqg-hf23-qpw2 lists affected ranges: npm electron >=39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0-beta.8 (fixed))
- Verified: https://github.com/advisories/GHSA-jfqg-hf23-qpw2 (GitHub-reviewed advisory GHSA-jfqg-hf23-qpw2 lists affected ranges: npm electron >=39.0.0-alpha.1 =40.0.0-alpha.1 =41.0.0-alpha.1 <41.0.0-beta.8)

Commands are suggestions: review each one before running it.