Loading vulnerability…
CVE-2026-50649 is a .NET deserialization-of-untrusted-data vulnerability. A .NET application can be exposed when it processes specially crafted untrusted serialized data, permitting an unauthorized attacker to execute code locally.
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.
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A .NET unsafe-deserialization vulnerability enabling local code execution.
A .NET deserialization flaw permitting local code execution through untrusted data.
A .NET vulnerability allowing local code execution through deserialization of untrusted data.
A .NET local code execution vulnerability via deserialization of untrusted data.
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.