# CVE-2019-25275: BartVPN 1.2.2 - 'BartVPNService' Unquoted Service Path

> Local attackers can execute arbitrary code with elevated privileges by exploiting an unquoted service path in BartVPN.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-p229-4hc8-7fpx

## What is CVE-2019-25275?

CVE-2019-25275 is a high-severity vulnerability in FileHorse BartVPN, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BartVPN 1.2.2 contains an unquoted service path vulnerability in the BartVPNService that allows local attackers to potentially execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted binary path by placing malicious executables in specific file system locations to hijack the service's execution context.

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

## Which versions are affected by CVE-2019-25275?


## How do I fix CVE-2019-25275?

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

## Is CVE-2019-25275 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25275 and fix it if it is affected.

What it is: CVE-2019-25275 is a high-severity vulnerability in FileHorse BartVPN, published on 4 Feb 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-2019-25275 in the wild and no public exploit code.

Affected product: FileHorse BartVPN. 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-2019-25275/ (Markdown: https://insights.sbomify.com/CVE-2019-25275/index.md)
```

## Sources

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

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