dbcve.org
.net FrameworkApplication · Microsoft

CVE-2026-47302

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 8.0.29 / 9.0.18 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allocation of resources without limits or throttling in .NET allows an unauthorized attacker to deny service over a network.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Denial of Service vulnerability in .NET where resource allocation occurs without proper limits or throttling, allowing an unauthenticated remote attacker to exhaust server resources over the network and deny service to legitimate users.

MitigationImplement resource limits, throttling, or quotas on the affected .NET component to prevent unbounded resource consumption. Apply any vendor-supplied patches for the affected .NET version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
.net FrameworkApplication
Affected:= 4.8= 4.6.2= 4.7= 4.7.1= 4.7.2= 3.5= 4.8.1
.netApplication
Affected:>= 8.0.0, < 8.0.29>= 9.0.0, < 9.0.18>= 10.0.0, < 10.0.6
Visual Studio 2022Application
Affected:>= 17.12.0, < 17.12.22>= 17.14.0, < 17.14.36
Visual Studio 2026Application
Affected:>= 18.7.0, < 18.7.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed .NET 8 runtime version
    Run 'dotnet --list-runtimes' and look for entries under 'Microsoft.WindowsDesktop.App' or 'Microsoft.AspNetCore.App' with 8.x version numbers
    Affected if The version listed is >= 8.0.0 and < 8.0.29
  2. Check installed .NET 9 runtime version
    Run 'dotnet --list-runtimes' and look for entries under 'Microsoft.WindowsDesktop.App' or 'Microsoft.AspNetCore.App' with 9.x version numbers
    Affected if The version listed is >= 9.0.0 and < 9.0.18
  3. Check installed .NET 10 runtime version
    Run 'dotnet --list-runtimes' and look for entries under 'Microsoft.WindowsDesktop.App' or 'Microsoft.AspNetCore.App' with 10.x version numbers
    Affected if The version listed is >= 10.0.0 and < 10.0.6
  4. Check .NET Framework version
    Check registry key 'HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' for Release value, or run 'reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release'
    Affected if The Release value corresponds to versions 4.8, 4.6.2, 4.7, 4.7.1, 4.7.2, 3.5, or 4.8.1 as defined by Microsoft version mappings
  5. Check Visual Studio 2022 version
    Open Visual Studio, go to Help > About Microsoft Visual Studio, or run 'devenv /version' from Developer Command Prompt for VS2022
    Affected if Version is >= 17.12.0 and < 17.12.22, or >= 17.14.0 and < 17.14.36
  6. Check Visual Studio 2026 version
    Open Visual Studio, go to Help > About Microsoft Visual Studio, or run 'devenv /version' from Developer Command Prompt for VS2026
    Affected if Version is >= 18.7.0 and < 18.7.4

You are affected if any installed .NET runtime, .NET Framework, Visual Studio 2022, or Visual Studio 2022 version falls within the affected version ranges listed for this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 8.0.29 / 9.0.18 / 10.0.6 or later
Fixed in 8.0.299.0.1810.0.6
Interim mitigation

Implement resource limits, throttling, or quotas on the affected .NET component to prevent unbounded resource consumption. Apply any vendor-supplied patches for the affected .NET version.

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47302 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data