CVE-2026-26171: .NET Denial of Service Vulnerability

Published Apr 13, 2026
·
Updated

.NET - SecurityFeatureBypass - Denial of Service and Security Feature Bypass via Unsafe Transforms in EncryptedXml

Other sources

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 uncontrolled resource consumption can give an attacker to the ability to perform a Denial of Service attack.

Announcement

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

CVSS Details

- Version: 3.1 - Severity: High - Score: 7.5 - Vector: 7.5: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H E:U/RL:O/RC:C - Weakness: CWE-400 CWE-611: Uncontrolled Resource Consumption Improper Restriction of XML External Entity Reference

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 packages versions listed below

<a name=".NET 10"></a>.NET 10 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=10.0.0, <=10.0.5; | 10.0.6

<a name=".NET 9"></a>.NET 9 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=9.0.0, <=9.0.14; | 9.0.15

<a name=".NET 8"></a>.NET 8 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=8.0.0, <=8.0.2; | 8.0.3

Advisory FAQ

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

If using an affected 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 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-26171

Acknowledgements

Ludvig Pedersen

Revisions

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

GitHub

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 uncontrolled resource consumption can give an attacker to the ability to perform a Denial of Service attack.

Announcement

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

CVSS Details

- Version: 3.1 - Severity: High - Score: 7.5 - Vector: 7.5: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H E:U/RL:O/RC:C - Weakness: CWE-400 CWE-611: Uncontrolled Resource Consumption Improper Restriction of XML External Entity Reference

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 packages versions listed below

<a name=".NET 10"></a>.NET 10 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=10.0.0, <=10.0.5; | 10.0.6

<a name=".NET 9"></a>.NET 9 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=9.0.0, <=9.0.14; | 9.0.15

<a name=".NET 8"></a>.NET 8 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.xml | >=8.0.0, <=8.0.2; | 8.0.3

Advisory FAQ

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

If using an affected 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 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-26171

Acknowledgements

Ludvig Pedersen

Revisions

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

GitHub

Uncontrolled resource consumption in .NET allows an unauthorized attacker to deny service over a network.

Microsoft

Affected Software

29 affected componentsFixes available
Microsoft .NET 10.0 installed on Windows
nuget/System.Security.Cryptography.Xml>=8.0.0<=8.0.2
8.0.3
nuget/System.Security.Cryptography.Xml>=9.0.0<=9.0.14
9.0.15
nuget/System.Security.Cryptography.Xml>=10.0.0<=10.0.5
10.0.6
Microsoft PowerShell 7.5
Microsoft PowerShell 7.6
All of the following
Microsoft .NET>=10.0.0<10.0.6
Any of the following
Apple macOS
Linux Linux kernel
All of the following
Microsoft .NET>=8.0.0<8.0.26
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
All of the following
Microsoft .NET>=9.0.0<9.0.15
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
Microsoft PowerShell>=7.5<7.5.6
Microsoft PowerShell>=7.6<7.6.1
Microsoft .NET 9.0 installed on Mac OS<9.0.15
9.0.15
Microsoft PowerShell 7.5<7.5.6
7.5.6
Microsoft .NET 8.0 installed on Mac OS<8.0.26
8.0.26
Microsoft PowerShell 7.6<7.6.1
7.6.1
Microsoft .NET 10.0 installed on Mac OS<10.0.6
10.0.6
Microsoft .NET 10.0 installed on Linux<10.0.6
10.0.6
Microsoft .NET 9.0 installed on Windows<9.0.15
9.0.15
Microsoft .NET 9.0 installed on Linux<9.0.15
9.0.15
Microsoft .NET 8.0 installed on Windows<8.0.26
8.0.26
Microsoft .NET 8.0 installed on Linux<8.0.26
8.0.26

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 8.0.3
  2. Upgrade

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

    Fixed in 9.0.15
  3. Upgrade

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

    Fixed in 10.0.6
  4. Upgrade

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

    Fixed in 9.0.15Patch KB5086097
  5. Upgrade

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

    Fixed in 8.0.26Patch KB5086096
  6. Upgrade

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

    Fixed in 7.5.6
  7. Upgrade

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

    Fixed in 10.0.6Patch KB5086095
  8. Upgrade

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

    Fixed in 7.6.1
  9. Upgrade

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

    Fixed in 10.0.6
  10. Upgrade

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

    Fixed in 8.0.3
  11. Upgrade

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

    Fixed in 9.0.15
  12. Operational

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

Event History

Apr 13, 2026
Data Sourced
via Red Hat·05:02 AM
DescriptionSeverityAffected Software
Apr 14, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
Updated
via Microsoft·02:00 PM
DescriptionWeakness
Updated
via Microsoft·02:00 PM
WeaknessAffected Software
CVE Published
via MITRE·04:58 PM
Data Sourced
via MITRE·04:58 PM
DescriptionSeverity
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
Affected Software
Advisory Published
via GitHub·11:31 PM
Data Sourced
via GitHub·11:31 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-26171?

CVE-2026-26171 is classified as a Denial of Service vulnerability that can potentially disrupt service availability.

2

How do I fix CVE-2026-26171?

To fix CVE-2026-26171, update to the latest version of .NET as specified in the official Microsoft patch releases.

3

Which versions of .NET are affected by CVE-2026-26171?

CVE-2026-26171 affects .NET versions 8.0, 9.0, and 10.0 across various operating systems.

4

What types of attacks could exploit CVE-2026-26171?

CVE-2026-26171 could be exploited through unsafe transforms in EncryptedXml that lead to Denial of Service conditions.

5

Is there any workaround for CVE-2026-26171?

Currently, there are no specific workarounds for CVE-2026-26171; applying the security update is recommended.

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