CVE-2025-26125
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-26125 is a high-severity Exposed IOCTL with Insufficient Access Control (CWE-782) vulnerability. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-26125 is a vulnerability in the IMFForceDelete driver of IObit Malware Fighter version 12.1.0, stemming from an exposed ioctl interface. This flaw, classified under CWE-782, enables attackers to perform arbitrary file deletions and escalate privileges. It has a CVSS v3.1 base score of 7.3 (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), indicating high impact potential with low attack complexity for local users.
A local attacker with low privileges can exploit this vulnerability by interacting with the exposed ioctl, typically requiring some user interaction to trigger. Successful exploitation allows arbitrary file deletion across the system and privilege escalation, potentially granting higher-level access and enabling further compromise of the affected host.
Advisories and proof-of-concept details are available in researcher publications, including GitHub repositories at https://github.com/ZeroMemoryEx/CVE-2025-26125 and https://github.com/ZeroMemoryEx/IObit-EoP, as well as a related post at https://x.com/zeromemoryex/status/1876878269200449819. Security practitioners should consult these for exploitation demonstrations and monitor IObit for official patches or updates to mitigate the issue.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6530
Vulnerability Data
An exposed ioctl in the IMFForceDelete driver of IObit Malware Fighter v12.1.0 allows attackers to arbitrarily delete files and escalate privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V8.2.1
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of access authorizations on system resources, which structurally stops an IOCTL from being exposed without proper controls.
AC-6 requires least-privilege assignments that limit which users or processes can reach privileged IOCTL functionality.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing IOCTL authorization during development.
Privileged access rights directly restrict who may invoke sensitive IOCTLs.
Secure development lifecycle includes design-time access-control requirements for device interfaces.
Application security requirements capture the need for proper IOCTL authorization.
Secure system architecture principles mandate least-privilege access to kernel interfaces.
Secure coding practices prevent omission of access-control checks on IOCTL handlers.