dbcve.org
.netApplication · Microsoft

CVE-2026-50524

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 Patch available 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
Improper validation of specified type of input in .NET Framework 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

A Denial of Service vulnerability in .NET Framework exists due to improper validation of a specific type of input. An unauthenticated attacker can send specially crafted input over a network to cause the affected system to become unresponsive or crash, resulting in service disruption.

MitigationApply available Microsoft security updates for .NET Framework. If patches are unavailable due to end-of-support status, consider migrating to .NET 6+ or implementing network-level filtering/rate limiting to mitigate exploitation.

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:>= 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 SDK version
    Run 'dotnet --version' in command prompt or PowerShell to retrieve the installed .NET SDK version
    Affected if The version returned is 8.0.0 through 8.0.28, 9.0.0 through 9.0.17, or 10.0.0 through 10.0.5
  2. Check .NET Runtime version via PowerShell
    Run 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Version | Select-Object -ExpandProperty Version' for .NET Framework, or 'dotnet --list-runtimes' for .NET Core/5+
    Affected if Any installed runtime version falls within the affected ranges (8.0.x before 8.0.29, 9.0.x before 9.0.18, 10.0.x before 10.0.6)
  3. Check Visual Studio 2022 version
    Run 'devenv /version' from Visual Studio installation path (typically C:\Program Files\Microsoft Visual Studio\2022\*\Common7\IDE\devenv.exe) or check Add/Remove Programs for version number
    Affected if The version is 17.12.0 through 17.12.21 or 17.14.0 through 17.14.35
  4. Check Visual Studio 2026 version
    Run 'devenv /version' from Visual Studio 2026 installation path or check Add/Remove Programs for version number
    Affected if The version is 18.7.0 through 18.7.3
  5. Identify network-exposed .NET applications
    Review IIS bindings, Kestrel/Katana configuration files, or any service logs showing network listeners. Check for open ports associated with .NET applications using 'netstat -ano | findstr LISTENING'
    Affected if The affected .NET versions are running and bound to network interfaces accessible from untrusted networks

You are affected if any installed .NET version (8.0.x before 8.0.29, 9.0.x before 9.0.18, 10.0.x before 10.0.6) or Visual Studio version (2022 17.12.x before 17.12.22, 2022 17.14.x before 17.14.36, or 2026 18.7.x before 18.7.4) is running and exposed to network input

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
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply available Microsoft security updates for .NET Framework. If patches are unavailable due to end-of-support status, consider migrating to .NET 6+ or implementing network-level filtering/rate limiting to mitigate exploitation.

Fix this in .net Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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