dbcve.org
.netApplication · Microsoft

CVE-2026-57108

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 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
Access of resource using incompatible type ('type confusion') in .NET Core 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

Type confusion vulnerability in .NET Core allows an unauthenticated remote attacker to cause denial of service. The vulnerability involves accessing a resource using an incompatible type, leading to service disruption.

MitigationApply Microsoft security patches for .NET Core once available. Monitor Microsoft Security Response Center for corresponding KB articles and CVE-2026-57108 updates.

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

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 Core SDK version
    Run 'dotnet --version' in a command prompt or terminal
    Affected if The version shown 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 installed .NET Core runtime versions
    Run 'dotnet --list-runtimes' and note the Microsoft.NETCore.App runtime entries
    Affected if Any runtime version listed falls within 8.0.x where x < 29, 9.0.x where x < 18, or 10.0.x where x < 6
  3. Identify all .NET Core installations on the system
    On Windows, check 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App' folder names; on Linux/macOS, check '/usr/share/dotnet/shared/Microsoft.NETCore.App' or '~/.dotnet/shared/Microsoft.NETCore.App'
    Affected if Any subfolder version matches the affected ranges listed above
  4. Check applicationhost.config or runtime configuration files
    Examine any 'runtimeconfig.json' or '.deps.json' files in application directories for 'Microsoft.NETCore.App' version entries
    Affected if The specified runtime version in these files is within the affected version ranges

If any installed .NET Core SDK or runtime version is 8.0.0-8.0.28, 9.0.0-9.0.17, or 10.0.0-10.0.5, the environment is vulnerable to CVE-2026-57108.

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.29 / 9.0.18 / 10.0.6 or later
Fixed in 8.0.299.0.1810.0.6
Interim mitigation

Apply Microsoft security patches for .NET Core once available. Monitor Microsoft Security Response Center for corresponding KB articles and CVE-2026-57108 updates.

Recommended fix High confidence

Upgrade to .NET 8.0.29+, 9.0.18+, or 10.0.6+ depending on your major version

  1. Identify the .NET SDK and runtime versions currently installed using `dotnet --list-sdks` and `dotnet --list-runtimes`
  2. For .NET 8.x deployments: upgrade to version 8.0.29 or later by running `dotnet --install 8.0.29` or updating via your package manager
  3. For .NET 9.x deployments: upgrade to version 9.0.18 or later by running `dotnet --install 9.0.18` or updating via your package manager
  4. For .NET 10.x deployments: upgrade to version 10.0.6 or later by running `dotnet --install 10.0.6` or updating via your package manager
  5. Rebuild and redeploy all affected applications to ensure they use the updated runtime
  6. Verify the update was successful by checking `dotnet --version` shows the patched version
Caveat Review Microsoft .NET release notes for any breaking changes between your current and target version before upgrading production systems

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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