Skip to content
major vulnerability· requires attention

Affects Microsoft .NET, a widely deployed platform; signature bypass can enable widespread auth/exec compromise across enterprise apps.

Cryptography

CVE-2026-47304

8.1
High
EPSS 0.22%Patch availableJul 15, 2026

.NET signature verification bypass allows forged data over network

common questions

Is CVE-2026-47304 being exploited?

Not confirmed. CVE-2026-47304 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2026-47304?

CVE-2026-47304 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47304?

Yes. A fix has been recorded for CVE-2026-47304. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-47304 affect?

CVE-2026-47304 affects .NET Framework, .NET Core / .NET 5+, ASP.NET applications, Apps using System.Security.Cryptography. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47304?

Apply vendor patch when released; restrict network exposure and perform additional signature validation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
.NET Framework.NET Core / .NET 5+ASP.NET applicationsApps using System.Security.Cryptography
impact

Bypass signature checks to accept forged messages or assemblies, enabling authentication bypass, tampering, or remote code execution over the network.

action required

Immediate action required

affected versions
Microsoft Microsoft .NET Framework 3.5
  • affected>= 3.5.0 and < 2.0.50727.8983 & 3.0.30729.8978
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
  • affected>= 4.7.0 and < 2.0.50727.9069 & 3.0.30729.9067 & 4.7.4143.0
Microsoft Microsoft .NET Framework 3.5 AND 4.8
  • affected>= 4.8.0 and < 2.0.50727.9069 & 3.0.30729.9067 & 4.8.4803.0
Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
  • affected>= 4.8.1 and < 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
  • affected>= 4.7.0 and < 4.7.4143.0
Microsoft Microsoft .NET Framework 4.8
  • affected>= 4.8.0 and < 4.8.4803.0
Microsoft Microsoft .NET Framework 4.8.1
  • affected>= 4.8.0.0 and < 4.8.9340.0
Microsoft Microsoft Visual Studio 2022 version 17.12
  • affected>= 17.12.0 and < 17.12.22
Microsoft Microsoft Visual Studio 2022 version 17.14
  • affected>= 17.14.0 and < 17.14.36
Microsoft Microsoft Visual Studio 2026 version 18.7
  • affected>= 18.0 and < 18.7.4
Microsoft .NET 10.0
  • affected>= 10.0.0 and < 10.0.10
Microsoft .NET 8.0
  • affected>= 8.0.0 and < 8.0.29
Microsoft .NET 9.0
  • affected>= 9.0.0 and < 9.0.18

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free