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

> A local attacker can escalate privileges to SYSTEM by exploiting an insecure log file deletion operation via symbolic links in Malwarebytes AdwCleaner.

- **Severity:** High 8.7 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A: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:** 17 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-w2v5-vxvg-mqgh

## What is CVE-2025-67905?

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

### Official description

Malwarebytes AdwCleaner before v.8.7.0 runs as Administrator and performs an insecure log file delete operation in which the target location is user-controllable, allowing a non-admin user to escalate privileges to SYSTEM via a symbolic link, a related issue to CVE-2023-28892. To exploit this, an attacker must create a file in a given folder path and intercept the application log file deletion flow.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-67905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67905 is a high-severity vulnerability in n/a, published on 17 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-2025-67905 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-67905/ (Markdown: https://insights.sbomify.com/CVE-2025-67905/index.md)
```

## Sources

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

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