Loading vulnerability…
CVE-2026-50528 is an incorrect-authorization vulnerability in .NET System.Net.Security TLS/SSL processing. An unauthenticated remote attacker can exploit vulnerable SslStream handling of TLS/SSL connections to bypass authentication-related authorization checks during secure communications. The issue affects .NET 8, .NET 9, and .NET 10 releases prior to the relevant security updates.
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.
41 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A .NET security-feature-bypass vulnerability caused by incorrect authorization.
A .NET security-feature-bypass vulnerability caused by incorrect authorization.
A .NET security-feature bypass caused by incorrect authorization.
A .NET security feature bypass vulnerability caused by incorrect authorization.
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.