CVE-2026-50527
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 · uneditedStack-based buffer overflow in .NET Framework allows an unauthorized attacker to deny service over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceA stack-based buffer overflow vulnerability in .NET Framework allows an unauthenticated remote attacker to cause a denial of service by sending specially crafted network requests to affected systems.
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= 4.8= 4.6.2= 4.7= 4.7.1= 4.7.2= 3.5= 4.8.1>= 8.0.0, < 8.0.29>= 9.0.0, < 9.0.18>= 10.0.0, < 10.0.6>= 17.12.0, < 17.12.22>= 17.14.0, < 17.14.36>= 18.7.0, < 18.7.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check .NET Framework version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (for .NET 4.x) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5 (for .NET 3.5). Look for the Version value in the Release or Version key.Affected if The version matches 4.8, 4.6.2, 4.7, 4.7.1, 4.7.2, 3.5, or 4.8.1 exactly as listed in the affected versions.
-
Check .NET (Core) versionOpen Command Prompt or PowerShell and run the command: dotnet --list-runtimes to display installed .NET runtime versions.Affected if The installed .NET version is greater than or equal to 8.0.0 but less than 8.0.29, OR greater than or equal to 9.0.0 but less than 9.0.18, OR greater than or equal to 10.0.0 but less than 10.0.6.
-
Check Visual Studio 2022 versionOpen Visual Studio, go to Help > About Microsoft Visual Studio, or run 'devenv /version' from Developer Command Prompt for VS 2022.Affected if The version is 17.12.0 through 17.12.21 (before 17.12.22), or 17.14.0 through 17.14.35 (before 17.14.36).
-
Check Visual Studio 2026 versionOpen Visual Studio 2026, go to Help > About Microsoft Visual Studio, or run 'devenv /version' from Developer Command Prompt for VS 2026.Affected if The version is 18.7.0 through 18.7.3 (before 18.7.4).
A system is affected if it has .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, or 4.8.1 installed, OR .NET 8.x/9.x/10.x within the vulnerable version ranges, OR Visual Studio 2022/2026 within the specified version ranges, and the system processes network requests with the vulnerable component exposed.
Generated from the published advisory. Verify against your own configuration.
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 data8.0.299.0.1810.0.6
Apply Microsoft security patches for .NET Framework once available, or implement network-level filtering and rate limiting to mitigate exploitation attempts until a patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50527 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50527 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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