Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

Microsoft Security Advisory CVE-2026-96958 - .NET and Visual Studio Denial of Service VulnerabilityGHSA-r955-8q5j-3h83

HIGH

GHSA-r955-8q5j-3h83 is a high-severity (CVSS 7.5) CWE-407 vulnerability in System.Security.Cryptography.Xml. A fix is available for System.Security.Cryptography.Xml — see the affected versions and patch details below.

Also known asBIT-dotnet-2026-96958BIT-dotnet-sdk-2026-96958CVE-2026-96958
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r955-8q5j-3h83.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-r955-8q5j-3h83 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected
.NETSystem.Security.Cryptography.Xml.NETSystem.Security.Cryptography.Xml.NETSystem.Security.Cryptography.Xml.NETSystem.Security.Cryptography.Xml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Executive summary

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

Signed XML fixes add input-depth and operation-count limits, prohibit DTD processing by default, validate entity references, bound encrypted-data candidate processing, and cap attributes and namespaces used by C14N transforms.

Announcement

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

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-407 (Inefficient Algorithmic Complexity)

Affected Platforms

  • Platforms: Windows, Linux, macOS
  • Architectures: All

<a name="affected-packages"></a>Affected Packages

The vulnerability affects Microsoft .NET projects that use an affected package version listed below.

Package nameAffected versionPatched version
System.Security.Cryptography.Xml>= 10.0.0, <= 10.0.1210.0.13
System.Security.Cryptography.Xml>= 11.0.0-preview.1, <= 11.0.0-rc.111.0.0-rc.2
System.Security.Cryptography.Xml>= 8.0.0, <= 8.0.48.0.5
System.Security.Cryptography.Xml>= 9.0.0, <= 9.0.209.0.21

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?

  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 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 runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

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-96958

Acknowledgements

  • Mateusz Gierblinski with Curios
  • Leandro Batista
  • Kevin Schmidt
  • Dr.-Ing Ashar Javed (@soaj1664ashar)

Revisions

V1.0 (10/13/2026): Advisory published.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSystem.Security.Cryptography.Xml≥ 10.0.0&&< 10.0.1310.0.13dotnet add package System.Security.Cryptography.Xml --version 10.0.13
.NETNuGetSystem.Security.Cryptography.Xml≥ 11.0.0-preview.1&&< 11.0.0-rc.211.0.0-rc.2dotnet add package System.Security.Cryptography.Xml --version 11.0.0-rc.2
.NETNuGetSystem.Security.Cryptography.Xml≥ 8.0.0&&< 8.0.58.0.5dotnet add package System.Security.Cryptography.Xml --version 8.0.5
.NETNuGetSystem.Security.Cryptography.Xml≥ 9.0.0&&< 9.0.219.0.21dotnet add package System.Security.Cryptography.Xml --version 9.0.21

Affected Products

2 products · 29 configurations
Application
.netmicrosoft
≥ 10.0.0 && < 10.0.13
1 version
11.0.0
Application
.net frameworkmicrosoft
7 versions
3.54.6.24.74.7.14.7.24.84.8.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for System.Security.Cryptography.Xml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update System.Security.Cryptography.Xml to 10.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r955-8q5j-3h83 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Frequently Asked Questions

## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Xml; System.Private.Xml. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Signed XML fixes add input-depth and operation-count limits, prohibit DTD processing by default, validate entity references, bound encrypted-data candidate processing, and cap attributes and namespaces used by C14N transforms. ## Announcement Announcement for this issue can be found at https://github.com
O3 Security · Impact-Aware SCA

Is GHSA-r955-8q5j-3h83 in your dependencies?

Find it across NuGet, including transitive dependencies.

Microsoft Security Advisory CVE-2026-96958 - .NET and…