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

Published Apr 3, 2026
·
Updated

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 security@electronjs.org

Other sources

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, 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. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.1, and 41.0.0.

MITRE

Affected Software

21 affected componentsFixes available
npm/electron>=41.0.0-alpha.1<41.0.0
41.0.0
npm/electron>=40.0.0-alpha.1<40.8.1
40.8.1
npm/electron>=39.0.0-alpha.1<39.8.1
39.8.1
npm/electron<38.8.6
38.8.6
electronjs Electron Node.js<38.8.6
electronjs Electron Node.js>=39.0.0<39.8.1
electronjs Electron Node.js>=40.0.0<40.8.1
electronjs Electron Node.js=41.0.0-alpha1
electronjs Electron Node.js=41.0.0-alpha2
electronjs Electron Node.js=41.0.0-alpha3
electronjs Electron Node.js=41.0.0-alpha4
electronjs Electron Node.js=41.0.0-alpha5
electronjs Electron Node.js=41.0.0-alpha6
electronjs Electron Node.js=41.0.0-beta1
electronjs Electron Node.js=41.0.0-beta2
electronjs Electron Node.js=41.0.0-beta3
electronjs Electron Node.js=41.0.0-beta4
electronjs Electron Node.js=41.0.0-beta5
electronjs Electron Node.js=41.0.0-beta6
electronjs Electron Node.js=41.0.0-beta7
electronjs Electron Node.js=41.0.0-beta8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 41.0.0
  2. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 40.8.1
  3. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 39.8.1
  4. Upgrade

    Upgrade npm/electron to a version that resolves this vulnerability.

    Fixed in 38.8.6
  5. Upgrade

    Upgrade electron to a version that resolves this vulnerability.

    Fixed in 38.8.6
  6. Upgrade

    Upgrade electron to a version that resolves this vulnerability.

    Fixed in 39.8.1
  7. Upgrade

    Upgrade electron to a version that resolves this vulnerability.

    Fixed in 40.8.1
  8. Upgrade

    Upgrade electron to a version that resolves this vulnerability.

    Fixed in 41.0.0
  9. Configuration

    Before calling `app.setAsDefaultProtocolClient(protocol)`, validate that `protocol` matches `/^[a-zA-Z][a-zA-Z0-9+.-]*$/` to prevent registry key path injection from externally or untrusted-derived input.

    Electron app.setAsDefaultProtocolClient (Windows registry write) protocol name validation = Validate protocol to match `/^[a-zA-Z][a-zA-Z0-9+.-]*$/` before passing it to app.setAsDefaultProtocolClient()

Event History

Apr 3, 2026
Advisory Published
via GitHub·02:41 AM
Data Sourced
via GitHub·02:41 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·11:50 PM
Data Sourced
via MITRE·11:50 PM
DescriptionSeverityWeakness
Apr 4, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Feb 28, 58277
Event
via NVD·06:19 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203