Loading vulnerability…
CVE-2026-50518 is a critical heap-based buffer overflow vulnerability in Windows DHCP Server. The flaw is triggered when the service processes specially crafted network requests containing malicious domain name data, leading to heap memory corruption. Because the vulnerable component is network-reachable and the issue is exploitable by an unauthorized attacker, successful exploitation can result in remote code execution without requiring prior authentication or user interaction.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical heap overflow remote code execution vulnerability in the DHCP server that can be exploited over the network without authentication.
A critical heap-based buffer overflow vulnerability in Windows DHCP Server that is unauthenticated and network-reachable, potentially enabling remote code execution.
A Windows DHCP Server remote code execution vulnerability highlighted in the patch release.
A critical remote code execution vulnerability affecting Windows DHCP Server.
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.