CVE-2026-50648: .NET Framework Denial of Service Vulnerability

Published Jul 14, 2026
·
Updated

.NET Framework Denial of Service Vulnerability

Other sources

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET XML Encryption (System.Security.Cryptography.Xml). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A denial of service vulnerability exists in the XML encryption implementation (EncryptedXml) in .NET 8, .NET 9, and .NET 10. An attacker could exploit this vulnerability by supplying crafted encrypted XML that causes uncontrolled resource consumption, resulting in denial of service.

Announcement

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

CVSS Details

- Version: 3.1 - Severity: High - Score: 7.5 - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

Affected Platforms

- Platforms: All - Architectures: All

<a name="affected-packages"></a>Affected Packages The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below

<a name=".NET 10.0"></a>.NET 10.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Xml | >= 10.0.0, <= 10.0.9 | 10.0.10

<a name=".NET 9.0"></a>.NET 9.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Xml | >= 9.0.0, <= 9.0.17 | 9.0.18

<a name=".NET 8.0"></a>.NET 8.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Xml | >= 8.0.0, <= 8.0.3 | 8.0.4

Advisory FAQ

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

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

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

To update the System.Security.Cryptography.Xml NuGet package, use one of the following methods:

NuGet Package Manager UI in Visual Studio: - Open your project in Visual Studio. - Right-click on your project in Solution Explorer and select "Manage NuGet Packages..." or navigate to "Project > Manage NuGet Packages". - In the NuGet Package Manager window, select the "Updates" tab. This tab lists packages with available updates from your configured package sources. - Select the package(s) you wish to update. You can choose a specific version from the dropdown or update to the latest available version. - Click the "Update" button.

Using the NuGet Package Manager Console in Visual Studio: - Open your project in Visual Studio. - Navigate to "Tools > NuGet Package Manager > Package Manager Console". - To update a specific package to its latest version, use the following Update-Package command:

Update-Package -Id System.Security.Cryptography.Xml

Using the .NET CLI (Command Line Interface): - Open a terminal or command prompt in your project's directory. - To update a specific package to its latest version, use the following add package command:

dotnet add package System.Security.Cryptography.Xml

Once you have updated the nuget package reference you must recompile and deploy your application. Additionally we recommend you update your runtime and/or SDKs, but it is not necessary to patch the vulnerability.

Other Information

Reporting Security Issues

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.

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. 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-2026-50648

Acknowledgements

41ae55e9310ff27fa6f26af4727e5590

Revisions

V1.0 (July 14, 2026): Advisory published.

GitHub

Allocation of resources without limits or throttling in .NET Framework allows an unauthorized attacker to deny service over a network.

Microsoft

Affected Software

97 affected componentsFixes available
Microsoft Visual Studio 2022=17.14
17.14.36
Microsoft .NET 9.0 installed on Windows<9.0.18
9.0.18
Microsoft Visual Studio 2022=17.12
17.12.22
Microsoft .NET 9.0 installed on Linux<9.0.18
9.0.18
Microsoft .NET 8.0 installed on Mac OS<8.0.29
8.0.29
Microsoft .NET 8.0 installed on Windows<8.0.29
8.0.29
Microsoft .NET 9.0 installed on Mac OS<9.0.18
9.0.18
Microsoft .NET 8.0 installed on Linux<8.0.29
8.0.29
Microsoft Visual Studio 2026=18.7
18.7.4
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0
Microsoft .NET Framework=4.8
4.8.4803.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4143.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0
Microsoft .NET Framework=3.5
2.0.50727.8983 & 3.0.30729.8978
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4143.0
Microsoft .NET Framework=3.5
2.0.50727.8983 & 3.0.30729.8978
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.91684.8.9340.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0
Microsoft .NET Framework=4.8
4.8.4803.0
Microsoft .NET Framework=4.8
4.8.4803.0
nuget/System.Security.Cryptography.Xml>=8.0.0<=8.0.3
8.0.4
nuget/System.Security.Cryptography.Xml>=9.0.0<=9.0.17
9.0.18
nuget/System.Security.Cryptography.Xml>=10.0.0<=10.0.9
10.0.10
Microsoft .NET 10.0 installed on Mac OS<10.0.10
10.0.10
Microsoft .NET 10.0 installed on Linux<10.0.10
10.0.10
All of the following
Microsoft .NET Framework=4.8
Any of the following
Microsoft Windows 10 1607
Microsoft Windows 10 1607
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
All of the following
Any of the following
Microsoft .NET Framework=4.6.2
Microsoft .NET Framework=4.7
Microsoft .NET Framework=4.7.1
Microsoft .NET Framework=4.7.2
Any of the following
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.8.1
Any of the following
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows 11 23h2
Microsoft Windows 11 23h2
Microsoft Windows 11 24h2
Microsoft Windows 11 24h2
Microsoft Windows 11 25h2
Microsoft Windows 11 25h2
Microsoft Windows 11 26h1
Microsoft Windows 11 26h1
Microsoft Windows Server 2022
All of the following
Any of the following
Microsoft .NET>=8.0.0<8.0.29
Microsoft .NET>=9.0.0<9.0.18
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.8
Any of the following
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows Server 2019
Microsoft Windows Server 2022
All of the following
Any of the following
Microsoft .NET Framework=3.5
Microsoft .NET Framework=4.7.2
Any of the following
Microsoft Windows 10 1607
Microsoft Windows 10 1607
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows Server 2016
Microsoft Windows Server 2019
All of the following
Microsoft .NET Framework=3.5
Any of the following
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
All of the following
Microsoft .NET>=10.0.0<10.0.6
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Visual Studio 2022>=17.12.0<17.12.22
Microsoft Visual Studio 2022>=17.14.0<17.14.36
Microsoft Visual Studio 2026>=18.7.0<18.7.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.14.36
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.0.18Patch KB5104033
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.12.22
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.29Patch KB5104032
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.7.4
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101000
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0Patch KB5101006
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0Patch KB5101008
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.4803.0Patch KB5101010
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4803.0Patch KB5101011
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101005
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4143.0Patch KB5100991
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0Patch KB5101003
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8983 & 3.0.30729.8978Patch KB5100984
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4143.0Patch KB5100990
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8983 & 3.0.30729.8978Patch KB5100985
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168Fixed in 4.8.9340.0Patch KB5101002
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101001
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0Patch KB5101004
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8983 & 3.0.30729.8978 & 4.7.4143.0Patch KB5099535
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9340.0Patch KB5100998
  22. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0Patch KB5100989
  23. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4803.0Patch KB5101009
  24. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4803.0Patch KB5101007
  25. Upgrade

    Upgrade nuget/System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 8.0.4
  26. Upgrade

    Upgrade nuget/System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 9.0.18
  27. Upgrade

    Upgrade nuget/System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 10.0.10
  28. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10Patch KB5104034
  29. Upgrade

    Upgrade System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 10.0.10
  30. Upgrade

    Upgrade System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 8.0.4
  31. Upgrade

    Upgrade System.Security.Cryptography.Xml to a version that resolves this vulnerability.

    Fixed in 9.0.18
  32. Operational

    After updating the System.Security.Cryptography.Xml NuGet package reference, recompile and redeploy your application.

Event History

Jul 14, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
SeverityAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
Updated
via Microsoft·02:00 PM
DescriptionSeverity
CVE Published
via MITRE·07:29 PM
Data Sourced
via MITRE·07:29 PM
DescriptionSeverity
Data Sourced
via Red Hat·08:05 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
RemedyAffected Software
Jul 16, 2026
Data Sourced
via Debian·03:46 AM
DescriptionAffected Software
Data Sourced
via Launchpad·03:46 AM
Description
Jul 18, 2026
Data Sourced
via Ubuntu·03:46 AM
RemedyDescriptionSeverityAffected Software
Jul 20, 2026
Advisory Published
via GitHub·10:49 PM
Data Sourced
via GitHub·10:49 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-50648?

CVE-2026-50648 has a severity rating of high, with a score of 7.5.

2

How do I fix CVE-2026-50648?

To fix CVE-2026-50648, you should apply the latest security updates from Microsoft for the .NET Framework.

3

What systems are affected by CVE-2026-50648?

CVE-2026-50648 affects various versions of Microsoft .NET Framework, including those installed on Windows, Mac OS, and Linux.

4

What is the nature of the vulnerability in CVE-2026-50648?

CVE-2026-50648 is a denial of service vulnerability that allows unauthorized attackers to exhaust resources over a network.

5

Is CVE-2026-50648 an easy vulnerability to exploit?

CVE-2026-50648 can be exploited without authentication, making it a significant risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203