# CVE-2025-66269: Unquoted Service Path in UPSilon2000V6.0(RupsMon and USBMate) running as SYSTEM

> Local attackers can escalate privileges to SYSTEM via unquoted service paths in UPSilon 2000 monitoring tools.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/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:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-2jxx-qpjm-mvc4

## What is CVE-2025-66269?

CVE-2025-66269 is a high-severity vulnerability in MegaTec Taiwan UPSilon2000V6.0, published on 26 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The RupsMon and USBMate services in UPSilon 2000 run with SYSTEM privileges and contain unquoted service paths. This allows a local attacker to perform path interception and escalate privileges if they have write permissions to the directories proceeding that of which the real service executables live in

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

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


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

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

## Is CVE-2025-66269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66269 is a high-severity vulnerability in MegaTec Taiwan UPSilon2000V6.0, published on 26 Nov 2025. 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-2025-66269 in the wild and no public exploit code.

Affected product: MegaTec Taiwan UPSilon2000V6.0. 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-66269/ (Markdown: https://insights.sbomify.com/CVE-2025-66269/index.md)
```

## Sources

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

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