Skip to content

Microsoft Security Advisory CVE-2026-33116 – .NET, .NET Framework, and Visual Studio Denial of Service Vulnerability

High severity GitHub Reviewed Published Apr 14, 2026 in dotnet/runtime • Updated Apr 17, 2026

Package

nuget System.Security.Cryptography.Xml (NuGet)

Affected versions

>= 10.0.0, <= 10.0.5
>= 9.0.0, <= 9.0.14
>= 8.0.0, <= 8.0.2

Patched versions

10.0.6
9.0.15
8.0.3

Description

Executive Summary:

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

A vulnerability exists in EncryptedXml class where an attacker can cause an infinite loop and perform a Denial of Service attack.

Announcement

Announcement for this issue can be found at dotnet/announcements#392

CVSS Details

  • Version: 3.1
  • Severity: High
  • Score: 7.5
  • Vector: 7.5 CVSS: 3.1AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
  • Weakness: CWE-835 CWE-400 CWE-20: Loop with Unreachable Exit Condition ('Infinite Loop') Uncontrolled Resource Consumption Improper Input Validation

Affected Platforms

  • Platforms: All
  • Architectures: All

Affected Packages

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

.NET 10

Package name Affected version Patched version
System.Security.Cryptography.Xml >=10.0.0, <=10.0.5 10.0.6

.NET 9

Package name Affected version Patched version
System.Security.Cryptography.Xml >=9.0.0, <=9.0.14 9.0.15

.NET 8

Package name Affected version Patched version
System.Security.Cryptography.Xml >=8.0.0, <=8.0.2 8.0.3

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?

To update the Using 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-33116

Acknowledgements

Ludvig Pedersen

Revisions

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

References

@bribrothers bribrothers published to dotnet/runtime Apr 14, 2026
Published by the National Vulnerability Database Apr 14, 2026
Published to the GitHub Advisory Database Apr 14, 2026
Reviewed Apr 14, 2026
Last updated Apr 17, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(73rd percentile)

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

Loop with Unreachable Exit Condition ('Infinite Loop')

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Learn more on MITRE.

CVE ID

CVE-2026-33116

GHSA ID

GHSA-37gx-xxp4-5rgx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.