Microsoft is issuing an update to the security advisory originally published on October 13, 2026. The advisory provides information about a vulnerability in Microsoft.AspNetCore.Identity and Microsoft.AspNetCore.Identity.UI and guidance on updating affected applications.
ASP.NET Core Identity password-reset and confirmation flows can send mail to the unvalidated request address instead of the user's stored canonical address.
This update also covers Identity UI and Blazor template paths. Updating a runtime, SDK, or template package does not rewrite application source that was generated previously.
The original announcement is https://github.com/dotnet/announcements/issues/457.
The published advisory is https://github.com/advisories/GHSA-x3vp-85cm-q97r.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CThe original advisory identifies the following runtime package intervals. These fixed versions do not address the additional generated-template paths described below.
Microsoft does not ship Windows ARM32 (win-arm) ASP.NET Core runtime packs for .NET 8, 9 or 10. Windows ARM64 (win-arm64) remains included below.
| Package | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.App.Runtime.linux-arm | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.linux-arm64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.linux-x64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.osx-arm64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.osx-x64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.win-x64 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
These package intervals retain the original fixes. They are separate from the additional November SDK-template repair.
| Package | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.Identity.UI | >= 8.0.0, <= 8.0.31 | 8.0.32 |
| Microsoft.AspNetCore.Identity.UI | >= 9.0.0, <= 9.0.20 | 9.0.21 |
| Microsoft.AspNetCore.Identity.UI | >= 10.0.0, <= 10.0.12 | 10.0.13 |
| Microsoft.AspNetCore.Identity.UI | >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.1.26425.128 | 11.0.0-rc.2.26504.105 |
The following SDK updates contain the corrected Blazor password-reset and resend-confirmation handlers. Each feature band has its own affected interval.
| Package | Affected version | Patched version |
|---|---|---|
| .NET SDK 8.0.1xx | >= 8.0.100, <= 8.0.133 | 8.0.134 |
| .NET SDK 8.0.4xx | >= 8.0.400, <= 8.0.427 | 8.0.428 |
| .NET SDK 9.0.1xx | >= 9.0.100, <= 9.0.123 | 9.0.124 |
| .NET SDK 9.0.3xx | >= 9.0.300, <= 9.0.320 | 9.0.321 |
| .NET SDK 10.0.1xx | >= 10.0.100, <= 10.0.114 | 10.0.115 |
| .NET SDK 10.0.4xx | >= 10.0.400, <= 10.0.403 | 10.0.404 |
| .NET SDK 11.0.1xx | >= 11.0.100-preview.1.26104.118, <= 11.0.100-rc.3.26522.148 | 11.0.100 |
These later package versions also contain the corrected Identity UI handlers. The original first-fixed versions remain listed above.
Additional patched Microsoft.AspNetCore.Identity.UI versions: 8.0.34, 9.0.23, 10.0.15, 11.0.0.
The standalone Microsoft.AspNetCore.Identity.UI 2.3.14 package contains the follow-up fix.
| Package | Affected version | Patched version |
|---|---|---|
| Microsoft.AspNetCore.Identity.UI | >= 2.3.0, <= 2.3.13 | 2.3.14 |
Check the package and SDK versions used by your application, and inspect any generated or copied Identity and Blazor account-recovery handlers. A handler that locates an account using the supplied email but sends the reset or confirmation message to that supplied address rather than the account's stored address requires repair.
Previously generated application code can remain affected even after its runtime, SDK, or template package is updated.
dotnet --info to check installed SDKs and runtimes.UserManager.GetEmailAsync(user), reject a missing or empty stored address, and send password-reset and confirmation messages only to that stored address, not Input.Email or another request-supplied recipient.Updating an installed runtime, SDK, Identity UI package, or template package does not perform step 2 for application-owned generated source.
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
You can ask questions about this issue in the ASP.NET Core discussion linked from the original announcement.
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
V1.0 (10/13/2026): Advisory published. V1.1 (11/10/2026): Updated SDK template and Identity UI affected versions and guidance for repairing previously generated application code.