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

> Local unprivileged users can manipulate privileged processes to gain higher privileges on Windows systems using DriveLock.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-c4hj-m2c4-rxf5

## What is CVE-2025-67781?

CVE-2025-67781 is a critical vulnerability in n/a, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in DriveLock 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5. Local unprivileged users can manipulate privileged processes to gain more privileges on Windows computers.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Drivelock Drivelock.

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

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

## Is CVE-2025-67781 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-55187](https://insights.sbomify.com/CVE-2025-55187/): Privilege escalation in n/a (critical 9.9)
- [CVE-2025-67790](https://insights.sbomify.com/CVE-2025-67790/): Denial of service in n/a (critical 9.8)
- [CVE-2025-67791](https://insights.sbomify.com/CVE-2025-67791/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-67793](https://insights.sbomify.com/CVE-2025-67793/): Privilege escalation in n/a (critical 9.8)
- [CVE-2025-67787](https://insights.sbomify.com/CVE-2025-67787/): Cross-site scripting in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67781 is a critical vulnerability in n/a, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67781 in the wild and no public exploit code.

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-67781/ (Markdown: https://insights.sbomify.com/CVE-2025-67781/index.md)
```

## Sources

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

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