dbcve.org
.netApplication · Microsoft

CVE-2026-33116

HIGH · 7.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 8.0.26 / 9.0.15 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Loop with unreachable exit condition ('infinite loop') in .NET, .NET Framework, Visual Studio allows an unauthorized attacker to deny service over a network.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 4mo 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

A vulnerability in .NET, .NET Framework, and Visual Studio contains a loop with an unreachable exit condition, creating an infinite loop that can be triggered by an unauthorized remote attacker to cause denial of service.

MitigationApply available security updates from Microsoft for affected .NET, .NET Framework, and Visual Studio installations to patch the vulnerable code path.

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
.netApplication
Affected:>= 10.0.0, < 10.0.6>= 8.0.0, < 8.0.26>= 9.0.0, < 9.0.15
.net FrameworkApplication
Affected:= 3.5= 4.7.2= 4.6.2= 4.7= 4.7.1= 4.8= 4.8.1

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 runtime version
    Run `dotnet --list-runtimes` or `dotnet --version` to list all installed .NET runtimes and their versions
    Affected if The installed .NET version falls within >= 10.0.0 and < 10.0.6, >= 8.0.0 and < 8.0.26, or >= 9.0.0 and < 9.0.15
  2. Check installed .NET Framework version
    Open Registry Editor and navigate to `HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full` (for .NET 4.x) or `HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5` (for .NET 3.5); check the Release value and compare to known version mappings, or run `Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Version, Release` in PowerShell
    Affected if The .NET Framework version is 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, or 4.8.1
  3. Check Visual Studio version
    Open Programs and Features or check `HKLM\SOFTWARE\Microsoft\VisualStudio\Setup\Instances` in the registry to identify installed Visual Studio instances and their versions
    Affected if Any Visual Studio instance is installed and the associated .NET components are present in an affected version range
  4. Identify network-exposed .NET services
    Review running services and listening ports using `netstat -ano | findstr LISTENING` or check any ASP.NET Core applications, WCF services, or other network-listeners configured in the environment
    Affected if Network services or applications using affected .NET/.NET Framework versions are exposed and listening for unauthenticated connections

The environment is affected if any installed .NET, .NET Framework, or Visual Studio version matches the specified affected ranges and network-facing components are in use.

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.

dbcve · scoped
Upgrade available Upgrade to 8.0.26 / 9.0.15 / 10.0.6 or later
Fixed in 8.0.269.0.1510.0.6
Interim mitigation

Apply available security updates from Microsoft for affected .NET, .NET Framework, and Visual Studio installations to patch the vulnerable code path.

Recommended fix High confidence

Upgrade to .NET 10.0.6 (for 10.x), .NET 9.0.15 (for 9.x), or .NET 8.0.26 (for 8.x)

  1. Identify the current .NET version installed by running 'dotnet --version' in the command line
  2. Determine which major .NET version line is in use (10.x, 9.x, or 8.x)
  3. For .NET 10.0.0-10.0.5: upgrade to .NET 10.0.6 by downloading and installing from https://dotnet.microsoft.com/download/dotnet/10.0
  4. For .NET 9.0.0-9.0.14: upgrade to .NET 9.0.15 by downloading and installing from https://dotnet.microsoft.com/download/dotnet/9.0
  5. For .NET 8.0.0-8.0.25: upgrade to .NET 8.0.26 by downloading and installing from https://dotnet.microsoft.com/download/dotnet/8.0
  6. Verify the upgrade was successful by running 'dotnet --version' and confirming it shows the fixed version
  7. Test applications in a staging environment before deploying to production
Caveat Patch updates within the same minor version (e.g., 8.0.25 to 8.0.26) typically have minimal breaking changes; however, test thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in .net Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33116 — 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-33116 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