NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-34773: Electron: Registry key path injection in app.setAsDefaultProtocolClient on Windows

mediumCVSS 3.1 4.7GHSA-mwmh-mq4g-g6gr

Impact On Windows, app.setAsDefaultProtocolClient(protocol) did not validate the protocol name before writing to the registry. Apps that pass untrusted input as the protocol name may allow an attacker to write to arbitrary subkeys under HKCU\Software\Classes\, potentially hijacking existing protocol handlers.

Published Apr 3, 2026 · Updated Apr 6, 2026

Affected packages

electron

Ecosystem
npm
Affected
< 38.8.6
Fixed in
38.8.6
Check
npm ls electron

electron

Ecosystem
npm
Affected
>= 39.0.0-alpha.1, < 39.8.1
Fixed in
39.8.1
Check
npm ls electron

electron

Ecosystem
npm
Affected
>= 40.0.0-alpha.1, < 40.8.1
Fixed in
40.8.1
Check
npm ls electron

electron

Ecosystem
npm
Affected
>= 41.0.0-alpha.1, < 41.0.0
Fixed in
41.0.0
Check
npm ls electron

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

On Windows, app.setAsDefaultProtocolClient(protocol) did not validate the protocol name before writing to the registry. Apps that pass untrusted input as the protocol name may allow an attacker to write to arbitrary subkeys under HKCU\Software\Classes\, potentially hijacking existing protocol handlers.

Apps are only affected if they call app.setAsDefaultProtocolClient() with a protocol name derived from external or untrusted input. Apps that use a hardcoded protocol name are not affected.

Workarounds

Validate the protocol name matches /^[a-zA-Z][a-zA-Z0-9+.-]*$/ before passing it to app.setAsDefaultProtocolClient().

Fixed Versions

  • 41.0.0
  • 40.8.1
  • 39.8.1
  • 38.8.6

For more information

If there are any questions or comments about this advisory, please email [[email protected]](mailto:[email protected])

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries