CVE-2026-34777 json
Electron: Incorrect origin passed to permission request handler for iframe requests
published 2026-04-03 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-18953 , GHSA-r5p7-gp4j-qhrx
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0, when an iframe requests fullscreen, pointerLock, keyboardLock, openExternal, or media permissions, the origin passed to session.setPermissionRequestHandler() was the top-level page's origin rather than the requesting iframe's origin. Apps that grant permissions based on the origin parameter or webContents.getURL() may inadvertently grant permissions to embedded third-party content. The correct requesting URL remains available via details.requestingUrl. Apps that already check details.requestingUrl are not affected. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.
Patch / fix
- npm electron 38.8.6, 39.8.1, 40.8.1, 41.0.0
- atom electron 38.8.6, 39.8.1, 40.8.1, 41.0.0
- electronjs electron 38.8.6, 39.8.1, 40.8.1, 41.0.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-34777 updated cvss 5.4
Electron: Electron: Unauthorized permission granting and information disclosure via incorrect iframe origin
-
Red Hat Build of Podman Desktop podman-desktop-macos-1-0, podman-desktop-windows-1-0 Red Hat Build of Podman Desktop - Tech Preview rhdesktop/rh-podman-desktop-ext-openshift-local-rhel10affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | electron | <38.8.6 >=39.0.0-alpha.1, <39.8.1 >=40.0.0-alpha.1, <40.8.1 >=41.0.0-alpha.1, <41.0.0 |
38.8.6 39.8.1 40.8.1 41.0.0 |
Affected products
- electron electron
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
github.com
/electron/electron/security/advisories/GHSA-r5p7-gp4j-qhrx
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-34777
advisory
-
github.com
/electron/electron
package
Sources
- CVE List CVE-2026-34777
- GitHub Advisory GHSA-r5p7-gp4j-qhrx
- NVD CVE-2026-34777
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.