Live › vulnerability › CVE-2026-106030
Go to dashboardNordVPN for Windows exposes a named pipe that accepts requests from low-privileged local processes. A local attacker can use it to stop unprotected Windows services and change their startup type to Manual, causing denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Windows machines running NordVPN for Windows before version 8.12 are exposed, and the attacker must already have a local account on the machine. Machines without NordVPN installed, or with it updated to 8.12 or later, are not affected. Protected services such as Windows Defender cannot be stopped through this flaw.
No product ranges from the sources yet.
8.128.12 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
NordVPN for Windows allows local attackers to stop unprotected Windows system services and change their startup type to Manual via named pipes. The NordVPN user-mode application allows a low-privileged attacker to act as a trusted process and connect to the named pipe "\.\pipe\nord-security\v1\NordVpnService\Server". The attacker can then invoke the "ISettingsGrpc.StopService" and "ISettingsGrpc.ChangeServiceStartType" methods with an arbitrary service name, allowing them to stop any unprotected Windows service and change its startup type. This leads to denial of service of critical system services. Services protected by Windows (PPL processes, Windows Tamper Protection), such as Windows Defender, cannot be stopped or reconfigured.
This issue was fixed in version 8.12
This page as .md · .json · in your agent: get_signal("CVE-2026-106030")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.