ASP.NET Core Identity Password-Recovery Account Takeover
CVE-2026-70175 is an improper-authentication vulnerability in ASP.NET Core Identity involving Microsoft.AspNetCore.Identity and Microsoft.AspNetCore.Identity.UI. Password-reset and confirmation flows can send email to an unvalidated address supplied in a request instead of the user's stored canonical address. This weakens account-recovery authentication and can allow an unauthorized network attacker to take over an account and elevate privileges. Affected product lines include .NET 8, 9, 10, and 11.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise an affected user's account and grant access to the account's application privileges. The vulnerability's CVSS v3.1 assessment indicates potentially high confidentiality, integrity, and availability impacts. The resulting access depends on the compromised account's permissions; operating-system privilege escalation and arbitrary code execution are not established.
If you can’t patch tonight, do this now.
No vulnerability-specific interim workaround is documented. Identify installed .NET versions and review application package references and self-contained deployments to determine exposure, then prioritize installation and deployment of the patched components.
Patch, then assume compromise.
Install the latest supported security update for the applicable .NET and ASP.NET Core branch. Identified patched versions are 8.0.32, 9.0.21, and 10.0.13; update affected package references accordingly. A vulnerability-specific fixed version for .NET 11 is not established here, so verify the applicable Microsoft update. Update Visual Studio when it supplies the installed SDK, and restart applications after updating the runtime or SDK. Recompile and redeploy affected self-contained applications, because updating the host runtime alone does not remediate them. Apply distribution-specific security packages where .NET is managed by the operating-system vendor.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
77 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.