Remote Code Execution in Windows DNS Server
CVE-2025-24064 is a remote code execution vulnerability in Windows DNS Server caused by a use-after-free condition. Improper handling of object lifetime in the DNS Server component can leave memory in a freed state while it is still referenced, enabling an unauthenticated attacker to trigger memory corruption over the network. Successful exploitation could allow attacker-controlled code execution in the context of the DNS Server service on a vulnerable system.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can result in remote code execution on a vulnerable Windows DNS Server. Because the flaw is reachable over the network and does not require prior authentication, compromise of an exposed DNS Server could permit full takeover of the affected service context, enabling follow-on actions such as installing malware, altering service behavior, pivoting within the environment, or disrupting name-resolution infrastructure.
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure of the DNS Server service to untrusted networks, restrict access to trusted clients and upstream systems through network segmentation and filtering, and minimize direct external reachability of affected DNS infrastructure. Increase monitoring for anomalous DNS service behavior and crashes that may indicate exploitation attempts. These measures only reduce exposure and do not eliminate the underlying vulnerability.
Patch, then assume compromise.
Apply the Microsoft security update released for CVE-2025-24064 as part of the March 2025 security updates. Prioritize patching all systems running the Windows DNS Server role, especially internet-reachable or otherwise untrusted-network-exposed servers. Standard remediation should include validating successful deployment across all affected Windows Server versions and removing unsupported systems from service or upgrading them to supported builds that include the fix.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.