CVE-2026-71328 is a heap-based buffer overflow in Microsoft.DiaSymReader.Native, affecting .NET and Visual Studio projects that use vulnerable package releases. While processing an MSFZ PDB file, the component can perform an out-of-bounds write. The underlying condition arises when stream-parsing logic allocates a heap buffer based on an attacker-controlled declared size and subsequently copies stream payload data without ensuring cumulative copied bytes remain within that allocation. A crafted file can declare a small size while containing a larger payload, corrupting adjacent heap memory.
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.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability fixed by updating to .NET SDK 8.0.131 and .NET Runtime 8.0.31.
A vulnerability fixed by the .NET SDK 8.0.131 and .NET Runtime 8.0.31 update; no technical impact details are provided.
An unspecified vulnerability addressed by the .NET SDK 9.0.121 and .NET Runtime 9.0.20 updates.
A vulnerability fixed by the .NET SDK 10.0.112 and .NET Runtime 10.0.12 updates; no technical vulnerability details are provided.
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.