Skip to content

← Actionable
High, CVSS 8.2

Microsoft Security Advisory CVE-2026-50528 – .NET Security Feature Bypass Vulnerability

CVE-2026-50528GHSA-qvw7-jm5c-6hqw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.netcore.app.runtime.win-x86 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.win-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-musl-x64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-arm 10.0.10, 9.0.18, 8.0.29; 7 more packages under Affected packages), 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

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-qvw7-jm5c-6hqw lists affected ranges: NuGet microsoft.netcore.app.runtime.linux-arm >=10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 <=8.0.28; NuGet…

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS
  • CVE-2026-50528: 0.61% estimated exploitation activity in the next 30 days; percentile 49.23 (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.

Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in .NET TLS/SSL (System.Net.Security). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A security feature bypass vulnerability exists in .NET 8, .NET 9, and .NET 10 when processing TLS/SSL connections. An attacker can exploit the SslStream implementation to bypass authorization checks during secure communication. Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/TBD CVSS Details - Version: 3.1 - Severity: High - Score: 8.2 - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N - Weakness: CWE-863 (Incorrect Authorization) Affected Platforms - Platforms: All - Architectures: All <a name="affected-packages"</aAffected Packages The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below <a name=".NET…

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

    Published from ghsa record GHSA-qvw7-jm5c-6hqw

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-2026-50528

Advisory: Microsoft Security Advisory CVE-2026-50528 – .NET Security Feature Bypass Vulnerability
IDs: CVE-2026-50528, GHSA-qvw7-jm5c-6hqw
Record: https://patchnext.com/advisories/cve-2026-50528 (revision 1, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.netcore.app.runtime.win-x86 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.win-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-musl-x64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-arm 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.osx-x64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-x64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.osx-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-musl-arm 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.win-arm 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.linux-musl-arm64 10.0.10, 9.0.18, 8.0.29; microsoft.netcore.app.runtime.win-x64 10.0.10, 9.0.18, 8.0.29. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.netcore.app.runtime.win-x86: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.win-arm64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-musl-x64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-arm64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-arm: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.osx-x64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-x64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.osx-arm64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-musl-arm: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.win-arm: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.linux-musl-arm64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18
- NuGet microsoft.netcore.app.runtime.win-x64: affected >= 10.0.0, <= 10.0.9; >= 9.0.0, <= 9.0.17; >= 8.0.0, <= 8.0.28; fixed in 8.0.29, 10.0.10, 9.0.18

## Suggested inspection (read-only)
- NuGet microsoft.netcore.app.runtime.win-x86: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-musl-x64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-arm: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.osx-x64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-x64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.osx-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-musl-arm: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-arm: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.linux-musl-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-x64: 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.netcore.app.runtime.win-x86, microsoft.netcore.app.runtime.win-arm64, microsoft.netcore.app.runtime.linux-musl-x64, microsoft.netcore.app.runtime.linux-arm64, microsoft.netcore.app.runtime.linux-arm, microsoft.netcore.app.runtime.osx-x64, microsoft.netcore.app.runtime.linux-x64, microsoft.netcore.app.runtime.osx-arm64, microsoft.netcore.app.runtime.linux-musl-arm, microsoft.netcore.app.runtime.win-arm, microsoft.netcore.app.runtime.linux-musl-arm64, microsoft.netcore.app.runtime.win-x64.
- 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-qvw7-jm5c-6hqw (GitHub-reviewed advisory GHSA-qvw7-jm5c-6hqw lists affected ranges: NuGet microsoft.netcore.app.runtime.linux-arm >=10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 =10.0.0 =9.0.0 =8.0.0 <=8.0.28; NuGet…)

Commands are suggestions: review each one before running it.

Loading voting…