Skip to content

← Actionable
Medium, CVSS 6.2

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

CVE-2023-36558GHSA-3fx3-85r4-8j3w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.aspnetcore.components 8.0.0, 7.0.14, 6.0.25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • NuGet microsoft.aspnetcore.components

    Affected
    >= 8.0.0-rc.2.23480.2, <= 8.0.0-rc.2.23480.2>= 7.0.0, <= 7.0.13>= 6.0.0, <= 6.0.24
    Fixed in
    8.0.0, 7.0.14, 6.0.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2023-36558: 1.08% estimated exploitation activity in the next 30 days; percentile 65.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Microsoft Security Advisory CVE-2023-36558: .NET Security Feature Bypass Vulnerability <a name="executive-summary"</aExecutive 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"</aMitigation 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"</aAffected software Any ASP.NET Core Blazor 6.0 application…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3fx3-85r4-8j3w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-36558

Advisory: Microsoft Security Advisory CVE-2023-36558: .NET Security Feature Bypass Vulnerability
IDs: CVE-2023-36558, GHSA-3fx3-85r4-8j3w
Record: https://patchnext.com/advisories/cve-2023-36558 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.aspnetcore.components 8.0.0, 7.0.14, 6.0.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.aspnetcore.components: affected >= 8.0.0-rc.2.23480.2, <= 8.0.0-rc.2.23480.2; >= 7.0.0, <= 7.0.13; >= 6.0.0, <= 6.0.24; fixed in 8.0.0, 7.0.14, 6.0.25

## Suggested inspection (read-only)
- NuGet microsoft.aspnetcore.components: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.aspnetcore.components.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3fx3-85r4-8j3w (GitHub-reviewed advisory GHSA-3fx3-85r4-8j3w lists affected ranges: NuGet microsoft.aspnetcore.components >=8.0.0-rc.2.23480.2 =7.0.0 =6.0.0 <=6.0.24)

Commands are suggestions: review each one before running it.

Loading voting…