# CVE-2026-47304: .NET Security Feature Bypass Vulnerability > An attacker can bypass security features by exploiting improper cryptographic signature verification in the .NET framework. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 14 Jul 2026 - **Updated:** 28 Oct 2026 - **Also known as:** BIT-dotnet-2026-47304, BIT-dotnet-sdk-2026-47304, ECHO-d94c-4487-662f, GHSA-g8r8-53c2-pm3f, MINI-7q2v-3hf9-p3g7, MINI-93h9-cw6p-63vv, MINI-g3vh-h9vm-jmcv, MINI-h67h-w6p7-w5qv, MINI-hgxx-r955-6xgg, MINI-j8x9-w4m9-cw8m, MINI-mr8r-v89x-rf8v, MINI-mww3-rv9r-7xfj, MINI-qgr5-28h8-g927, MINI-vvhm-v96r-wwfv, ROOT-APP-NUGET-CVE-2026-47304, UBUNTU-CVE-2026-47304 ## What is CVE-2026-47304? CVE-2026-47304 is a high-severity vulnerability in Microsoft .Net, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network. Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2026-47304? 8 open source packages ship an affected version, including System.Security.Cryptography.Xml, dotnet and dotnet-sdk. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `System.Security.Cryptography.Xml` | NuGet | From 10.0.0 | 10.0.10 | | `System.Security.Cryptography.Xml` | NuGet | From 10.0.0 | 10.0.10 | | `System.Security.Cryptography.Xml` | NuGet | From 8.0.0 | 8.0.4 | | `System.Security.Cryptography.Xml` | NuGet | From 8.0.0 | 8.0.4 | | `System.Security.Cryptography.Xml` | NuGet | From 9.0.0 | 9.0.18 | | `System.Security.Cryptography.Xml` | NuGet | From 9.0.0 | 9.0.18 | | `dotnet` | Bitnami | From 8.0.0 | 8.0.29, 9.0.18, 10.0.6 | | `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.29, 9.0.18, 10.0.6 | Products: Microsoft .Net, Microsoft .Net Framework, Microsoft Visual Studio 2017, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026. ## How do I fix CVE-2026-47304? Upgrade System.Security.Cryptography.Xml to a fixed version for your release line: 10.0.10, 8.0.4 or 9.0.18. ## Is CVE-2026-47304 being exploited? There is no known exploitation of CVE-2026-47304 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-47304 and fix it if it is affected. What it is: CVE-2026-47304 is a high-severity vulnerability in Microsoft .Net, published on 14 Jul 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-47304 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.10 - System.Security.Cryptography.Xml (NuGet): affected from 10.0.0; fixed in 10.0.10 - System.Security.Cryptography.Xml (NuGet): affected from 8.0.0; fixed in 8.0.4 - System.Security.Cryptography.Xml (NuGet): affected from 8.0.0; fixed in 8.0.4 - System.Security.Cryptography.Xml (NuGet): affected from 9.0.0; fixed in 9.0.18 - System.Security.Cryptography.Xml (NuGet): affected from 9.0.0; fixed in 9.0.18 - dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.29, 9.0.18, 10.0.6 - dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.29, 9.0.18, 10.0.6 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-47304/ (Markdown: https://insights.sbomify.com/CVE-2026-47304/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47304 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47304 - OSV: https://osv.dev/vulnerability/CVE-2026-47304 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47304/ Summaries are generated and may contain mistakes; the official description above is the record.