CVE-2026-47300 is an elevation of privilege vulnerability in ASP.NET Core caused by an incorrect implementation of an authentication algorithm. The flaw affects multiple supported ASP.NET Core delivery lines through affected .NET releases, and is also addressed through corresponding Visual Studio servicing updates. A remote attacker who is already authorized can exploit the authentication logic weakness over the network to obtain privileges beyond those originally granted. Microsoft rates the issue as Important and assigns CVSS v3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating low attack complexity, no user interaction requirement, and high potential impact across confidentiality, integrity, and availability.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An elevation of privilege vulnerability in ASP.NET Core.
A privilege escalation vulnerability in ASP.NET Core caused by an incorrect implementation of an authentication algorithm, allowing an authorized attacker to elevate privileges 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.