Quick answers
- Is CVE-2026-34773 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34773 being exploited in the wild.
- How severe is CVE-2026-34773?
- Medium severity, with a CVSS score of 4.7, 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-34773?
- 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-34773 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-34773?
- 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
A registry key path injection vulnerability exists in Electron's 'app.setAsDefaultProtocolClient' API on Windows. The root cause is improper neutralization of special elements (CWE-74) and improper input validation (CWE-20) of the protocol name string before it is written to the Windows Registry. An attacker who can influence the input passed to this function can write to arbitrary subkeys under 'HKCU\Software\Classes\', enabling the hijacking of existing protocol handlers. This exploit requires the target application to derive the protocol name from untrusted or external input. The issue is patched 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 < 39.8.1, >= 40.0.0-alpha.1 < 40.8.1, >= 41.0.0-alpha.1 < 41.0.0
Identifiers
- CVE-2026-34773
- GHSA-mwmh-mq4g-g6gr
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-04: disclosed: CVE published to NVD