# CVE-2026-96959: .NET Denial of Service Vulnerability > An unauthorized attacker can cause a denial of service in .NET Framework by exploiting uncontrolled resource allocation. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Oct 2026 - **Updated:** 29 Oct 2026 - **Also known as:** BIT-dotnet-2026-96959, BIT-dotnet-sdk-2026-96959, ECHO-a9c4-3288-b534, GHSA-c399-9853-6jmj, MINI-3jvm-rppm-h6h2, MINI-7434-xc6v-2f44, MINI-hhgh-m833-rrjv, MINI-jj65-pj8r-fxfg, MINI-p7p3-g8xm-vqrp, MINI-rxfg-626x-jxg7, ROOT-APP-NUGET-CVE-2026-96959, UBUNTU-CVE-2026-96959 ## What is CVE-2026-96959? CVE-2026-96959 is a high-severity denial of service vulnerability in Microsoft .Net, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service over a network. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2026-96959? 10 open source packages ship an affected version, including System.Security.Cryptography.Xml, dotnet and dotnet-sdk. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `System.Security.Cryptography.Xml` | NuGet | From 10.0.0 | 10.0.13 | | `System.Security.Cryptography.Xml` | NuGet | From 10.0.0 | 10.0.13 | | `System.Security.Cryptography.Xml` | NuGet | From 11.0.0-preview.1 | 11.0.0-rc.2 | | `System.Security.Cryptography.Xml` | NuGet | From 11.0.0-preview.1 | 11.0.0-rc.2 | | `System.Security.Cryptography.Xml` | NuGet | From 8.0.0 | 8.0.5 | | `System.Security.Cryptography.Xml` | NuGet | From 8.0.0 | 8.0.5 | | `System.Security.Cryptography.Xml` | NuGet | From 9.0.0 | 9.0.21 | | `System.Security.Cryptography.Xml` | NuGet | From 9.0.0 | 9.0.21 | | `dotnet` | Bitnami | From 8.0.0 | 8.0.5, 9.0.21, 10.0.13 | | `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.5, 9.0.21, 10.0.13 | Products: Microsoft .Net, Microsoft .Net Framework. ## How do I fix CVE-2026-96959? Upgrade System.Security.Cryptography.Xml to a fixed version for your release line: 10.0.13, 11.0.0-rc.2, 8.0.5 or 9.0.21. ## Is CVE-2026-96959 being exploited? There is no known exploitation of CVE-2026-96959 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft .Net - [CVE-2024-43498](https://insights.sbomify.com/CVE-2024-43498/): .NET and Visual Studio Remote Code Execution Vulnerability (critical 9.8) - [CVE-2024-0057](https://insights.sbomify.com/CVE-2024-0057/): NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability (critical 9.1) - [CVE-2026-96957](https://insights.sbomify.com/CVE-2026-96957/): .NET Security Feature Bypass Vulnerability (high 8.8) - [CVE-2026-69439](https://insights.sbomify.com/CVE-2026-69439/): .NET and Visual Studio Elevation of Privilege Vulnerability (high 8.8) - [CVE-2026-71328](https://insights.sbomify.com/CVE-2026-71328/): .NET and Visual Studio Remote Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-96959 and fix it if it is affected. What it is: CVE-2026-96959 is a high-severity denial of service vulnerability in Microsoft .Net, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-96959 in the wild and no public exploit code. Affected packages and fixed versions: - System.Security.Cryptography.Xml (NuGet): affected from 10.0.0; fixed in 10.0.13 - System.Security.Cryptography.Xml (NuGet): affected from 10.0.0; fixed in 10.0.13 - System.Security.Cryptography.Xml (NuGet): affected from 11.0.0-preview.1; fixed in 11.0.0-rc.2 - System.Security.Cryptography.Xml (NuGet): affected from 11.0.0-preview.1; fixed in 11.0.0-rc.2 - System.Security.Cryptography.Xml (NuGet): affected from 8.0.0; fixed in 8.0.5 - System.Security.Cryptography.Xml (NuGet): affected from 8.0.0; fixed in 8.0.5 - System.Security.Cryptography.Xml (NuGet): affected from 9.0.0; fixed in 9.0.21 - System.Security.Cryptography.Xml (NuGet): affected from 9.0.0; fixed in 9.0.21 - dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.5, 9.0.21, 10.0.13 - dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.5, 9.0.21, 10.0.13 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-96959/ (Markdown: https://insights.sbomify.com/CVE-2026-96959/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96959 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96959 - OSV: https://osv.dev/vulnerability/CVE-2026-96959 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-96959/ Summaries are generated and may contain mistakes; the official description above is the record.