dbcve.org
.net FrameworkApplication · Microsoft

CVE-2026-50649

HIGH · 7.8 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 →
81/100
Remediation priority · High
No privileges 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
Deserialization of untrusted data in .NET allows an unauthorized attacker to execute code locally.

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 deserialization vulnerability in .NET allows an unauthorized attacker to execute code locally through deserialization of untrusted data. This type of flaw occurs when applications deserialize data from untrusted sources without proper validation, potentially allowing malicious payloads to instantiate arbitrary objects or execute code during the deserialization process.

MitigationAvoid deserializing data from untrusted sources; implement allowlist validation for deserialized types; keep .NET runtime and all third-party libraries updated to patched versions; consider disabling BinaryFormatter if not needed.

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.1= 4.8= 4.6.2= 4.7= 4.7.1= 4.7.2= 3.5
.netApplication
Affected:>= 8.0.0, < 8.0.29>= 9.0.0, < 9.0.18
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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 8 runtime version
    Run 'dotnet --version' or 'dotnet --list-runtimes' to see installed .NET 8.x versions
    Affected if Version is >= 8.0.0 and < 8.0.29
  2. Check .NET 9 runtime version
    Run 'dotnet --version' to see if .NET 9.x is installed and note the full version number
    Affected if Version is >= 9.0.0 and < 9.0.18
  3. Check .NET Framework version
    Open Registry Editor and navigate to 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' to view the Release value, then map it to the version using Microsoft's version reference table
    Affected if Release value corresponds to .NET Framework 4.8.1, 4.8, 4.7.2, 4.7.1, 4.7, 4.6.2, or 3.5
  4. Check Visual Studio 2026 version
    Open Visual Studio, go to Help > About Microsoft Visual Studio, or run 'devenv /version' from Developer Command Prompt for Visual Studio
    Affected if Version is >= 18.7.0 and < 18.7.4
  5. Audit code for BinaryFormatter usage
    Search project source code for 'BinaryFormatter' type usage, specifically looking for BinaryFormatter.Deserialize() calls or BinaryFormatter constructor in any .cs files
    Affected if BinaryFormatter is used to deserialize data in the application
  6. Identify deserialization of untrusted data
    Review application code and configuration to identify endpoints, files, or data sources that accept serialized data from external or untrusted inputs without allowlist validation
    Affected if The application deserializes data from network inputs, user uploads, or other untrusted sources

You are affected if you run any of the vulnerable .NET/.NET Framework/Visual Studio versions AND your application uses deserialization on untrusted data, particularly with BinaryFormatter.

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 / 18.7.4 or later
Fixed in 8.0.299.0.1818.7.4
Interim mitigation

Avoid deserializing data from untrusted sources; implement allowlist validation for deserialized types; keep .NET runtime and all third-party libraries updated to patched versions; consider disabling BinaryFormatter if not needed.

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-50649 — 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-50649 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