Protocol-handler hijacking via unchecked registry path

Path injection in affected Electron releases allows attackers to hijack Windows protocol handlers through a crafted protocol name. The Windows implementation of app.setAsDefaultProtocolClient(protocol) uses the unchecked protocol string to form a path below HKCU\Software\Classes, allowing path separators to redirect the registry write into attacker-selected subkeys. Exposure requires an application to derive the protocol argument from external input; hardcoded names are unaffected, and the reported consequence is registry integrity loss rather than disclosure or interruption.