Quick answers
- Is CVE-2026-34777 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34777 being exploited in the wild.
- How severe is CVE-2026-34777?
- Medium severity, with a CVSS score of 5.4, published 4 April 2026.
- Which products and versions are affected?
- electron (npm) SEMVER:introduced=0,fixed=38.8.6.
- Is there a fix for CVE-2026-34777?
- Yes. electron (npm): upgrade to 38.8.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34777 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34777?
- Check whether you run electron (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- electron (npm): upgrade to 38.8.6 or later
npm install electron@38.8.6
Technical details
An origin validation error (CWE-346) exists in Electron's permission handling logic. When an iframe requests permissions for fullscreen, pointerLock, keyboardLock, openExternal, or media, the origin passed to the 'session.setPermissionRequestHandler()' callback is incorrectly set to the top-level page's origin instead of the iframe's actual origin. Attackers can exploit this by embedding malicious content that inherits the permissions of the trusted parent window if the application relies on the 'origin' parameter or 'webContents.getURL()' for authorization. The vulnerability is mitigated if developers manually verify 'details.requestingUrl'. Patches are available in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.
Affected products
- ElectronJS Electron < 38.8.6, 39.0.0-alpha.1 to < 39.8.1, 40.0.0-alpha.1 to < 40.8.1, 41.0.0-alpha.1 to < 41.0.0
Identifiers
- CVE-2026-34777
- GHSA-r5p7-gp4j-qhrx
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-04: disclosed: CVE published to NVD