# CVE-2026-106030: Missing Authorization in NordVPN for Windows

> Local attackers can stop arbitrary Windows services via named pipes due to missing authorization, causing denial of service.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-g85w-3p3f-vrj3

## What is CVE-2026-106030?

CVE-2026-106030 is a medium-severity missing authorization vulnerability in NordVPN, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-106030?


## How do I fix CVE-2026-106030?

No fix has been published for CVE-2026-106030 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106030 being exploited?

There is no known exploitation of CVE-2026-106030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106030 and fix it if it is affected.

What it is: CVE-2026-106030 is a medium-severity missing authorization vulnerability in NordVPN, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106030 in the wild and no public exploit code.

Affected product: NordVPN. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106030/ (Markdown: https://insights.sbomify.com/CVE-2026-106030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106030
- OSV: https://osv.dev/vulnerability/CVE-2026-106030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106030/
Summaries are generated and may contain mistakes; the official description above is the record.