# NordVPN Windows flaw allows service shutdown

Published: 2026-10-16 · Severity: routine
Canonical: https://vorant.io/reports/4604ca06-36e5-547c-a844-6d7a5bbb793d/nordvpn-windows-flaw-allows-service-shutdown

> A fixed NordVPN for Windows flaw let local attackers abuse a named pipe to stop and disable unprotected system services.

CERT Polska coordinated disclosure of CVE-2026-106030, a local privilege-abuse vulnerability in the NordVPN Windows client. The NordVPN user-mode application exposes a named pipe (\\.\pipe\nord-security\v1\NordVpnService\Server) that a low-privileged local attacker can connect to and impersonate a trusted process. By invoking the ISettingsGrpc.StopService and ISettingsGrpc.ChangeServiceStartType gRPC methods with an arbitrary service name, the attacker can stop any unprotected Windows service and change its startup type to Manual, resulting in denial of service against affected system services.

Services hardened with Windows Protected Process Light (PPL) or Tamper Protection — such as Windows Defender — are not affected by this technique, limiting the blast radius to unprotected services. The issue requires local code execution/low-privileged local access to exploit; there is no remote vector and no indication of in-the-wild exploitation. NordVPN addressed the issue in version 8.12.

Defenders running NordVPN for Windows in managed environments should ensure clients are updated to version 8.12 or later. Security teams can additionally monitor for unexpected named-pipe connections to NordVPN service pipes or unusual service state/startup-type changes initiated by non-administrative processes as a detection opportunity, though patching remains the primary mitigation.

## Mentioned in this report

- Vulnerabilities: CVE-2026-106030

## Detection guidance (public sample)

### Non-NordVPN Process Connecting to NordVPN Service Named Pipe

ATT&CK: T1559

A process outside the NordVPN install directory connects to the NordVpnService gRPC named pipe, as in the CVE-2026-106030 abuse to stop or reconfigure arbitrary services. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

```yaml
title: Non-NordVPN Process Connecting to NordVPN Service Named Pipe
description: Detects a pipe connection (Sysmon event 18) to the NordVPN service gRPC
  pipe from a process that is not located in a NordVPN install directory. CVE-2026-106030
  abuses this pipe to call StopService and ChangeServiceStartType with arbitrary service
  names. Requires Sysmon pipe connect logging.
references:
- https://cert.pl/en/posts/2026/10/CVE-2026-106030
tags:
- attack.privilege-escalation
- attack.t1559
- attack.impact
- attack.t1489
logsource:
  category: pipe_created
  product: windows
detection:
  selection:
    EventType: ConnectPipe
    PipeName|contains: \nord-security\v1\NordVpnService
  filter_nordvpn:
    Image|contains:
    - \NordVPN\
    - \Nord Security\
    - \NordSec\
  condition: selection and not filter_nordvpn
falsepositives:
- Third-party NordVPN management or diagnostic tools installed outside the standard
  directory
- Security products that enumerate named pipes
level: high
id: 9d0eb183-7b87-56a5-a1ca-9b61516a761c
status: experimental
author: Vorant
```

### Service Start Type Changed to Manual Outside Typical Maintenance

ATT&CK: T1489

Service Control Manager reports a service start type changed to demand start (Manual), the second step of the NordVPN pipe abuse for service denial of service. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

```yaml
title: Service Start Type Changed to Manual Outside Typical Maintenance
description: Detects Service Control Manager event 7040 where a service start type
  is changed to demand start (Manual). The NordVPN CVE-2026-106030 abuse uses ChangeServiceStartType
  to set arbitrary services to Manual after stopping them. Correlate with NordVPN
  pipe connections or service stop events (7036) from the same host. Tune the filter
  for environment-specific servicing.
tags:
- attack.impact
- attack.t1489
logsource:
  product: windows
  service: system
detection:
  selection:
    Provider_Name: Service Control Manager
    EventID: 7040
    param3|contains: demand start
  filter_servicing:
    param1:
    - Background Intelligent Transfer Service
    - Windows Modules Installer
    - Microsoft Edge Update Service (edgeupdate)
    - Microsoft Edge Update Service (edgeupdatem)
    - Google Update Service (gupdate)
    - Google Update Service (gupdatem)
  condition: selection and not filter_servicing
falsepositives:
- Windows servicing and software installers changing service start types
- Administrators deliberately setting services to Manual
level: low
id: 6f8ad42e-7ad7-56a0-9f02-e9eae1df8abb
status: experimental
author: Vorant
references:
- https://cert.pl/en/posts/2026/10/CVE-2026-106030
```

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://cert.pl/en/posts/2026/10/CVE-2026-106030

---

This is the free public brief from Vorant Threat Intelligence. When citing, attribute "Vorant" and link https://vorant.io/reports/4604ca06-36e5-547c-a844-6d7a5bbb793d/nordvpn-windows-flaw-allows-service-shutdown.
In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), live profiles of the actors and CVEs it names, and the vendor research on the same campaign. Slack alerts fire on the vendors, sectors and countries a reader follows. A new account starts with three days of all of it, no card: https://vorant.io/signup