Loading vulnerability…
CVE-2026-47304 is a .NET security feature bypass vulnerability caused by improper verification of cryptographic signatures. The flaw allows a remote, unauthenticated attacker to exploit weaknesses in signature validation logic and bypass an authentication-related security control. Available reporting characterizes the issue as an improper verification condition in .NET rather than a memory corruption flaw, and maps it to cryptographic signature verification weaknesses. Affected software includes supported Microsoft Visual Studio releases that ship vulnerable .NET components prior to the fixed versions identified by Microsoft.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A security feature bypass vulnerability in .NET.
A security feature bypass vulnerability in .NET caused by improper verification of cryptographic signatures, affecting certain Microsoft Visual Studio 2022 and Visual Studio 2026 versions and reachable over a network.
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.