You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes.
Description
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
[{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop","defaultStatus":"affected","cpes":["cpe:/a:redhat:podman_desktop:1"]},{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop - Tech Preview","defaultStatus":"affected","cpes":["cpe:/a:redhat:podman_desktop:0"]}]
[{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop","defaultStatus":"affected","collectionURL":"https://access.redhat.com/downloads/content/package-browser/","packageName":"podman-desktop-macos-1-0","cpes":["cpe:/a:redhat:podman_desktop:1"]},{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop","defaultStatus":"affected","collectionURL":"https://access.redhat.com/downloads/content/package-browser/","packageName":"podman-desktop-windows-1-0","cpes":["cpe:/a:redhat:podman_desktop:1"]},{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop - Tech Preview","defaultStatus":"affected","collectionURL":"https://access.redhat.com/downloads/content/package-browser/","packageName":"rhdesktop/rh-podman-desktop-ext-openshift-local-rhel10","cpes":["cpe:/a:redhat:podman_desktop:0"]}]
[{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop","defaultStatus":"affected","cpes":["cpe:/a:redhat:podman_desktop:1"]},{"vendor":"Red Hat","product":"Red Hat Build of Podman Desktop - Tech Preview","defaultStatus":"affected","cpes":["cpe:/a:redhat:podman_desktop:0"]}]
OR
*cpe:2.3:a:electronjs:electron:41.0.0:alpha1:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:alpha2:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:alpha3:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:alpha4:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:alpha5:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:alpha6:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta1:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta2:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta3:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta4:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta5:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta6:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:41.0.0:beta7:*:*:*:node.js:*:*
*cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* versions from (including) 39.0.0 up to (excluding) 39.8.0
*cpe:2.3:a:electronjs:electron:*:*:*:*:*:node.js:*:* versions from (including) 40.0.0 up to (excluding) 40.7.0
New CVE Received from GitHub, Inc.4/03/2026 9:16:39 PM
Action
Type
Old Value
New Value
Added
Description
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.