NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

CVE-2023-36558 — Microsoft.AspNetCore.Comp…

MEDIUM

CVE-2023-36558 is a medium-severity (CVSS 5.5) vulnerability in Microsoft.AspNetCore.Components. A fix is available for Microsoft.AspNetCore.Components — see the affected versions and patch details below.

Microsoft Security Advisory CVE-2023-36558: .NET Security Feature Bypass Vulnerability

Also known asBIT-aspnet-core-2023-36558BIT-dotnet-2023-36558BIT-dotnet-sdk-2023-36558GHSA-3fx3-85r4-8j3w
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-36558.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk
0.00%0.53%1.06%1.58%0.4%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
.NETMicrosoft.AspNetCore.Components.NETMicrosoft.AspNetCore.Components.NETMicrosoft.AspNetCore.Components

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft Security Advisory CVE-2023-36558: .NET Security Feature Bypass Vulnerability

<a name="executive-summary"></a>Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 6.0, ASP.NET Core 7.0 and, ASP.NET Core 8.0 RC2. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability.

A security feature bypass vulnerability exists in ASP.NET where an unauthenticated user is able to bypass validation on Blazor server forms which could trigger unintended actions.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/288

<a name="mitigation-factors"></a>Mitigation factors

This vulnerability only affects ASP.NET Core Blazor apps. Other application types, including ASP.NET Core apps which do not utilize Blazor, are not affected.

<a name="affected-software"></a>Affected software

  • Any ASP.NET Core Blazor 6.0 application running on .NET 6.0.24 or earlier.
  • Any ASP.NET Core Blazor 7.0 application running on .NET 7.0.13 or earlier.
  • Any ASP.NET Core Blazor 8.0 application running on .NET 8.0 RC2.

If your application uses the following package versions, ensure you update to the latest version of .NET.

<a name=".NET 7"></a>.NET 8.0

Package nameAffected versionPatched version
Microsoft.AspNetCore.Components8.0.0-rc.2.23480.28.0.0

<a name=".NET 7"></a>.NET 7.0

Package nameAffected versionPatched version
Microsoft.AspNetCore.Components>= 7.0.0, < 7.0.13>7.0.14

<a name=".NET 7"></a>.NET 6.0

Package nameAffected versionPatched version
Microsoft.AspNetCore.Components>= 6.0.0, < 6.0.246.0.25

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you're exposed to the vulnerability.

<a name="how-fix"></a>How do I fix the issue?

  • To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
  • If you are using one of the affected packages, please update to the patched version listed above.
  • If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;
.NET Core SDK (reflecting any global.json):

 Version:   7.0.200
 Commit:    8473146e7d

Runtime Environment:

 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.300\

Host (useful for support):

  Version: 76.0.5
  Commit:  8473146e7d

.NET Core SDKs installed:

  7.0.200 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:

  Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

.NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET 8.0 or .NET 7.0 or .NET 6.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

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.

External Links

CVE-2023-36558

Revisions

V1.0 (November 14, 2023): Advisory published.

Version 1.0

Last Updated 2023-11-14

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.Components≥ 8.0.0-rc.2.23480.2&&< 8.0.08.0.0dotnet add package Microsoft.AspNetCore.Components --version 8.0.0
.NETNuGetMicrosoft.AspNetCore.Components≥ 7.0.0&&< 7.0.147.0.14dotnet add package Microsoft.AspNetCore.Components --version 7.0.14
.NETNuGetMicrosoft.AspNetCore.Components≥ 6.0.0&&< 6.0.256.0.25dotnet add package Microsoft.AspNetCore.Components --version 6.0.25

Affected Products

3 products · 11 configurations
Application
.netmicrosoft
≥ 7.0.0 && < 7.0.14
1 version
8.0.0
Application
asp.net coremicrosoft
≥ 7.0.0 && < 7.0.14
1 version
8.0.0
Application
visual studio 2022microsoft
≥ 17.7 && < 17.7.7
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Components, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.AspNetCore.Components to 8.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36558 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2023-36558 (CC BY 4.0)
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet60-dotnet-0:6.0.125-1.el7_9RHSA-2023:7259
Red Hat Enterprise Linux 8dotnet8.0-0:8.0.100-2.el8_9RHSA-2023:7254
Red Hat Enterprise Linux 8dotnet7.0-0:7.0.114-1.el8_9RHSA-2023:7256
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.125-1.el8_9RHSA-2023:7258
Red Hat Enterprise Linux 9dotnet8.0-0:8.0.100-2.el9_3RHSA-2023:7253
Red Hat Enterprise Linux 9dotnet7.0-0:7.0.114-1.el9_3RHSA-2023:7255
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.125-1.el9_3RHSA-2023:7257
UbuntuMEDIUM

Frequently Asked Questions

# Microsoft Security Advisory CVE-2023-36558: .NET Security Feature Bypass Vulnerability ## <a name="executive-summary"></a>Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 6.0, ASP.NET Core 7.0 and, ASP.NET Core 8.0 RC2. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability. A security feature bypass vulnerability exists in ASP.NET where an unauthenticated user is able to bypass validation on Blazor server forms which could trigger unintended actio
O3 Security · Impact-Aware SCA

Is CVE-2023-36558 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2023-36558: Microsoft.AspNetCore — Fixed in 8.0.0