CVE-2026-42987 is a use-after-free vulnerability in Windows Deployment Services (WDS), a Windows Server role used for network-based operating system deployment. The flaw can be triggered over the network in systems with WDS enabled, and available reporting indicates exploitation is associated with crafted TFTP traffic and a race condition during deployment-related processing. By causing WDS to access memory after it has been freed, an unauthenticated attacker may corrupt process state and achieve remote code execution on the affected server.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in the Windows Server OS installation utility involving a race condition and malicious TFTP traffic that could allow server hijacking during deployment.
A use-after-free remote code execution vulnerability in Windows Deployment Services.
A critical remote code execution vulnerability in Windows Deployment Services caused by a use-after-free flaw.
A remote code execution vulnerability in Windows Deployment Services.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.