dbcve.org
.netApplication · Microsoft

CVE-2026-32203

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
Stack-based buffer overflow in .NET and Visual Studio allows an unauthorized attacker to deny service over a network.

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 stack-based buffer overflow vulnerability exists in .NET and Visual Studio that allows an unauthenticated remote attacker to cause a denial of service by sending specially crafted network requests to affected systems.

MitigationApply Microsoft security updates for .NET and Visual Studio when released, or disable network-facing interfaces if possible until patches are available.

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
Visual Studio 2022Application
Affected:>= 17.12.0, < 17.12.19>= 17.14.0, < 17.14.30
Visual Studio 2026Application
Affected:>= 18.4.0, < 18.4.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 .NET SDK version
    Open a command prompt and run `dotnet --version` to see the installed .NET SDK version. For runtime only, run `dotnet --list-runtimes` to see all installed .NET runtimes.
    Affected if The version shown is 10.0.0 through 10.0.5, 8.0.0 through 8.0.25, or 9.0.0 through 9.0.14.
  2. Check Visual Studio version
    Open Visual Studio, go to Help > About Microsoft Visual Studio, or run `vswhere -version -property productVersion` from the Visual Studio installation directory.
    Affected if The version shown is 17.12.0 through 17.12.18, 17.14.0 through 17.14.29, or 18.4.0 through 18.4.3.
  3. Verify .NET installations across machines
    If managing multiple systems, use a centralized inventory tool or script to query each endpoint for .NET versions via `dotnet --list-runtimes` or by checking registry key HKEY_LOCAL_MACHINE\SOFTWARE\dotnet\Setup\InstalledVersions.
    Affected if Any system returns a .NET version within the affected ranges listed above.

Your environment is affected if any installed instance of .NET (8.0.x, 9.0.x, or 10.0.x) or Visual Studio 2022/2026 falls within the specific version ranges listed as vulnerable.

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 Microsoft security updates for .NET and Visual Studio when released, or disable network-facing interfaces if possible until patches are available.

Recommended fix High confidence

.NET 8.0.26+, .NET 9.0.15+, .NET 10.0.6+ | Visual Studio 2022 17.12.19+ or 17.14.30+ | Visual Studio 2026 18.4.4+

  1. Identify which .NET runtime and SDK versions are installed using 'dotnet --list-sdks' and 'dotnet --list-runtimes'
  2. For .NET 8.0.x deployments: upgrade to .NET 8.0.26 or later by running 'dotnet --install 8.0.26' or updating via your package manager
  3. For .NET 9.0.x deployments: upgrade to .NET 9.0.15 or later by running 'dotnet --install 9.0.15' or updating via your package manager
  4. For .NET 10.0.x deployments: upgrade to .NET 10.0.6 or later
  5. For Visual Studio 2022: update to version 17.12.19 or later, or version 17.14.30 or later via Visual Studio Installer
  6. For Visual Studio 2026: update to version 18.4.4 or later via Visual Studio Installer
  7. Rebuild and redeploy any applications using the updated .NET SDK
  8. Verify the update was successful by checking 'dotnet --version' shows the patched version
Caveat Minor/patch updates typically have no breaking changes; however, review release notes for any behavior changes in the specific minor version

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

Fix this in .net Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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