CVE-2026-40372: ASP.NET Core Data Protection Authentication Cookie Forgery Privilege Escalation
- Vendor
- Microsoft Corporation
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
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.
Recent activity
76 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.