# CVE-2025-61161: Privilege escalation in n/a

> Local attackers can escalate privileges to SYSTEM by placing a malicious DLL in a specific directory loaded by Evope Collector.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-c4qv-5j2j-52m7

## What is CVE-2025-61161?

CVE-2025-61161 is a high-severity vulnerability in n/a, published on 29 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DLL hijacking vulnerability in Evope Collector 1.1.6.9.0 and related components load the wtsapi32.dll library from an uncontrolled search path (C:\ProgramData\Evope). This allows local unprivileged attackers to execute arbitrary code or escalate privileges to SYSTEM by placing a crafted DLL in that location. The vulnerable component is Evope.Service.exe, which runs with SYSTEM privileges and automatically loads the DLL on startup or reboot.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-61161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61161 is a high-severity vulnerability in n/a, published on 29 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61161 exists.

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

## Sources

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

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