CVE-2026-50528

Summary

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

Severity

high

CVSS

8.2

EPSS

0.6% (p49)

CWE

CWE-302, CWE-863

Also known as

GHSA-qvw7-jm5c-6hqw#Microsoft.NetCore.App.Runtime.linux-arm

Published

2026-07-20

Updated

2026-07-20

Advisory details

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

Affected Packages

The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below

.NET 10.0

.NET 9.0

.NET 8.0

Advisory FAQ

How do I know if I am affected?

If using a package listed in affected packages, you're exposed to the vulnerability.

How do I fix the issue?

1. To fix the issue please install the latest version of .NET. 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.
2. If your application references the vulnerable nuget package, update the package reference to the patched version. You can list the versions you have installed by running the dotnet --info command.

Once you have installed the updated

References

• https://github.com/advisories/GHSA-qvw7-jm5c-6hqw
• https://github.com/dotnet/runtime/security/advisories/GHSA-qvw7-jm5c-6hqw
• https://nvd.nist.gov/vuln/detail/CVE-2026-50528
• https://github.com/dotnet/announcements/issues/417
• https://github.com/dotnet/runtime/issues/130713
• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50528

Related advisories

• GHSA-cxf3-9h37-7rr8#github.com/labstack/echo/v5 — critical · Go/github.com/labstack/echo/v5
• GHSA-cxf3-9h37-7rr8#github.com/labstack/echo/v4 — critical · Go/github.com/labstack/echo/v4
• CVE-2026-77366 — critical · npm/obsidian-tc
• CVE-2026-77459 — critical · Go/github.com/argoproj/argo-cd/v2
• CVE-2026-68582 — critical · Go/code.vikunja.io/api
• CVE-2026-105851 — critical · npm/payload
• CVE-2026-100721 — critical · npm/vm2
• CVE-2026-92951 — critical · npm/vm2

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Summarize with AI

ChatGPTClaudePerplexity