# CVE-2025-26125: Missing authorization in n/a

> Attackers can exploit an exposed ioctl in the IMFForceDelete driver to arbitrarily delete files and escalate privileges.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-xcxv-mc83-gmw5

## What is CVE-2025-26125?

CVE-2025-26125 is a high-severity missing authorization vulnerability in n/a, published on 17 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An exposed ioctl in the IMFForceDelete driver of IObit Malware Fighter v12.1.0 allows attackers to arbitrarily delete files and escalate privileges.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

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


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

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

## Is CVE-2025-26125 being exploited?

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

Public exploit code:

- ( 0day ) Local Privilege Escalation in IObit Malware Fighter (github_poc): https://github.com/ZeroMemoryEx/CVE-2025-26125

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26125 is a high-severity missing authorization vulnerability in n/a, published on 17 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26125 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-26125/ (Markdown: https://insights.sbomify.com/CVE-2025-26125/index.md)
```

## Sources

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

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