Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2019-6494: Arbitrary File Deletion via IOCTL in IObit Malware Fighter 6.2 IMFForceDelete.sys

Published Apr 30, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS1.1%66th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Iobit
IdentifiersCVE-2019-6494CWE-732

A vulnerability in the IMFForceDelete.sys driver of IObit Malware Fighter 6.2 allows a low privileged user to send IOCTL 0x8016E000 with a user-defined string specifying a file path. The driver will then delete the specified file, bypassing standard access controls and permissions. This allows arbitrary file deletion on the system by any local user.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local attacker can delete any file on the system, including critical system files or files belonging to other users, leading to potential denial of service, privilege escalation, or system instability.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the vulnerable driver to trusted users only. Monitor for and block suspicious IOCTL requests to IMFForceDelete.sys. Remove or disable the driver if not required until a patched version is available.

Remediation

Patch, then assume compromise.

Update to a version of IObit Malware Fighter where IMFForceDelete.sys properly validates user privileges and restricts file deletion operations to authorized users only. Ensure that the driver does not allow arbitrary file paths from unprivileged users.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IobitMalware Fighterapplication
FAQ

Frequently asked questions

Is CVE-2019-6494 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-6494?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-6494.
Is there a patch for CVE-2019-6494?
Update to a version of IObit Malware Fighter where IMFForceDelete.sys properly validates user privileges and restricts file deletion operations to authorized users only. Ensure that the driver does not allow arbitrary file paths from unprivileged users.
What products are affected by CVE-2019-6494?
Iobit Malware Fighter.
How severe is CVE-2019-6494?
CVE-2019-6494 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 1.1% (66th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.