# CVE-2025-66575: VeeVPN 1.6.1 - Unquoted Service Path Remote Code Execution

> Attackers can execute arbitrary code with LocalSystem privileges via an unquoted service path in VeeVPN during startup or reboot.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-388g-pgp3-x5mx

## What is CVE-2025-66575?

CVE-2025-66575 is a high-severity vulnerability in VeePN VeeVPN, published on 4 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

VeeVPN 1.6.1 contains an unquoted service path vulnerability in the VeePNService that allows remote attackers to execute code during startup or reboot with escalated privileges. Attackers can exploit this by providing a malicious service name, allowing them to inject commands and run as LocalSystem.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2025-66575?

It affects 1 product.


Products: Veepn Veepn.

## How do I fix CVE-2025-66575?

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

## Is CVE-2025-66575 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66575 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66575 and fix it if it is affected.

What it is: CVE-2025-66575 is a high-severity vulnerability in VeePN VeeVPN, published on 4 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66575 exists.

Affected product: VeePN VeeVPN. 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-2025-66575/ (Markdown: https://insights.sbomify.com/CVE-2025-66575/index.md)
```

## Sources

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

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