Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighCISA KEVExploited in the wildPublic exploit

Remote Code Execution in Windows NTFS

IdentifiersCVE-2025-24993CWE-122· Heap-based Buffer Overflow

CVE-2025-24993 is a heap-based buffer overflow vulnerability in Windows NTFS. The available reporting describes it as an NTFS memory corruption issue that can be triggered when a user mounts a specially crafted malicious VHD, leading to a heap-based buffer overflow and enabling local code execution by an unauthorized attacker. Multiple sources in the provided content state that Microsoft marked this vulnerability as exploited in the wild at disclosure time.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation can result in local code execution on the target Windows system. Because the flaw is a heap-based buffer overflow in the NTFS file system path, exploitation gives an attacker the ability to run code in the context reached through the vulnerable NTFS processing path after the malicious VHD is mounted. The vulnerability was reported as actively exploited in the wild, increasing operational risk.

Mitigation

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

Until patches are fully deployed, reduce exposure by preventing or tightly restricting mounting of untrusted VHD files, limiting user ability to attach disk images, and blocking delivery paths for malicious disk images from email, web downloads, and removable media where feasible. Apply least-privilege controls for users who can mount virtual disks and monitor for suspicious VHD mounting activity. These are compensating controls only; the authoritative mitigation is vendor patching.

Remediation

Patch, then assume compromise.

Apply Microsoft's March 2025 security updates for Windows that address CVE-2025-24993. Prioritize patching systems that process VHDs or are exposed to untrusted removable or disk-image media. Ensure supported Windows versions are fully updated with the vendor fix.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.