CVE-2024-35264 is a remote code execution vulnerability affecting .NET 8 / ASP.NET Core 8 and associated Visual Studio tooling through data corruption in Kestrel HTTP/3 request handling. The flaw is described as a use-after-free condition that can be triggered during request body processing when an attacker interrupts or closes an HTTP/3 stream at a precise time, creating a race condition. Successful exploitation depends on winning that race and causing the application to access previously deallocated memory, which can lead to memory corruption and attacker-controlled code execution in the context of the vulnerable application process.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Use-after-free remote code execution vulnerability affecting .NET and Visual Studio Code, exploitable by winning a race condition through interruption of an HTTP/3 stream during request body processing.
Remote code execution vulnerability in .NET and Visual Studio involving an HTTP/3 race condition.
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.