Skip to main content
Mallory
CriticalVulnerability

CVE-2026-40372: ASP.NET Core Data Protection Authentication Cookie Forgery Privilege Escalation

Published Apr 21, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.1Critical · v3.1
EPSS11.2%96th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-40372CWE-347 · Improper Verification of…

CVE-2026-40372 is an elevation-of-privilege vulnerability in ASP.NET Core Data Protection affecting Microsoft.AspNetCore.DataProtection NuGet package versions 10.0.0 through 10.0.6. The flaw resides in the managed authenticated encryptor, where HMAC validation can be performed incorrectly because the validation tag is computed over the wrong bytes of the payload and the computed hash may then be discarded. This breaks integrity verification for Data Protection payloads and allows forged protected data to be accepted as valid. In practical terms, an unauthenticated remote attacker can abuse the flaw to forge authentication cookies and tamper with other protected application artifacts, and some protected payloads may also be decrypted. Reported affected artifacts include authentication cookies, antiforgery tokens, TempData, and OpenID Connect state. The issue was fixed in Microsoft.AspNetCore.DataProtection 10.0.7.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow remote privilege escalation by enabling an attacker to forge authentication material accepted by the target application. This can result in impersonation of other users, elevation to privileged application identities, disclosure of protected data, and modification of application data. Reporting also indicates that some exploitation paths can lead to issuance of legitimately signed follow-on artifacts such as refreshed sessions, API keys, or password-reset material, which may remain valid after patching unless keys and dependent artifacts are rotated. Microsoft reporting further states that affected deployments could in some cases be driven to SYSTEM-level compromise on the host. Availability impact has not been reported as a primary consequence.

Mitigation

If you can’t patch tonight, do this now.

If an affected application was internet-exposed during the vulnerable window, rotate the ASP.NET Core Data Protection key ring after patching. Revoke all existing Data Protection keys where operationally feasible so previously forged access and attacker-induced signed artifacts cannot continue to validate. Force reauthentication and reissue antiforgery material and other protected state as needed. Audit and rotate long-lived application-layer artifacts created during exposure, including refresh tokens, access tokens, API keys, password-reset material, and similar signed objects. Review server logs for anomalous high-volume requests to endpoints that process protected payloads.

Remediation

Patch, then assume compromise.

Upgrade Microsoft.AspNetCore.DataProtection to version 10.0.7 or later, rebuild affected applications, and redeploy so the corrected validation routine is loaded at runtime. Verify that the vulnerable NuGet package is no longer being used in deployed builds, including transitive dependency paths and container images where applicable. Review whether affected applications issued long-lived signed artifacts during the vulnerable window and revoke, expire, or reissue them as appropriate.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationAsp.Net Coreapplication
Microsoft CorporationVisual Studio 2026application
FAQ

Frequently asked questions

Is CVE-2026-40372 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-40372 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-40372?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-40372.
Is there a patch for CVE-2026-40372?
Upgrade Microsoft.AspNetCore.DataProtection to version 10.0.7 or later, rebuild affected applications, and redeploy so the corrected validation routine is loaded at runtime. Verify that the vulnerable NuGet package is no longer being used in deployed builds, including transitive dependency paths and container images where applicable.
What products are affected by CVE-2026-40372?
Microsoft Corporation Asp.Net Core and Microsoft Corporation Visual Studio 2026.
How severe is CVE-2026-40372?
CVE-2026-40372 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 11.2% (96th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

76 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
register securityNews · Apr 24, 2026Remote Desktop security beefed up with hard-to-read messages • The RegisterAn elevation-of-privilege vulnerability in .NET affecting versions 10.0.0 through 10.0.6, caused by forged authentication cookies and serious enough to prompt a follow-up update.Read more ↗scworldNews · Apr 23, 2026Microsoft patches critical ASP.NET Core privilege escalation vulnerability | brief | SC MediaA critical privilege escalation vulnerability in ASP.NET Core Data Protection cryptographic APIs caused by a regression in Microsoft.AspNetCore.DataProtection NuGet packages that incorrectly compute HMAC validation tags, potentially allowing attackers to forge payloads, bypass authenticity checks, decrypt protected payloads, and gain elevated privileges.Read more ↗socprime blogNews · Apr 23, 2026CVE-2026-40372: ASP.NET Core Privilege EscalationA high-impact ASP.NET Core privilege-escalation vulnerability in the Data Protection cryptographic APIs caused by improper verification of a cryptographic signature, enabling forged protected payloads, disclosure/modification of data, and potential SYSTEM-level privilege escalation under specific conditions.Read more ↗arstechnica securityNews · Apr 22, 2026Microsoft issues emergency update for macOS and Linux ASP.NET threat - Ars TechnicaA high-severity ASP.NET Core DataProtection vulnerability caused by faulty verification of cryptographic signatures, allowing unauthenticated attackers to forge authentication payloads and gain SYSTEM privileges on affected Linux or macOS systems.Read more ↗
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity65Community discussion across Reddit, Mastodon, and other social sources.