dbcve.org
.netApplication · Microsoft

CVE-2026-45490

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 8.0.28 / 9.0.17 or later.
See remediation →
80/100
Remediation priority · High
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
Improper authorization in .NET allows an authorized attacker to elevate privileges locally.

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 · low confidence

Improper authorization vulnerability in Microsoft .NET framework allows a local user who already has some level of access (authorized attacker) to elevate their privileges to a higher permission level within the system.

MitigationApply Microsoft security patches for .NET when released; follow least-privilege principles for local user accounts and monitor for unusual privilege escalation activity.

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.28>= 9.0.0, < 9.0.17>= 10.0.0, < 10.0.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 SDK version installed
    Run `dotnet --version` in command prompt or PowerShell to retrieve the installed .NET SDK version
    Affected if The displayed version falls within 8.0.0-8.0.27, 9.0.0-9.0.16, or 10.0.0-10.0.8
  2. Check .NET Runtime version
    Run `dotnet --list-runtimes` to display all installed .NET runtimes and their versions
    Affected if Any runtime version listed matches 8.0.x where x < 28, 9.0.x where x < 17, or 10.0.x where x < 9
  3. Verify Windows-specific .NET installation via registry
    Open Registry Editor and navigate to `HKLM\SOFTWARE\dotnet\Setup\InstalledVersions` or query with `Get-ItemProperty -Path 'HKLM:\SOFTWARE\dotnet\Setup\InstalledVersions' -Name 'Version' -ErrorAction SilentlyContinue` in PowerShell
    Affected if The Version value corresponds to an affected version range (8.0.0-8.0.27, 9.0.0-9.0.16, or 10.0.0-10.0.8)
  4. Check .NET worker service or application runtime
    For applications using .NET, inspect the `runtimeconfig.json` or the published application's runtime dependencies to identify the targeted .NET version
    Affected if The application targets or runs on an affected .NET version

The system is affected if any installed .NET SDK, runtime, or application targets a version within 8.0.0-8.0.27, 9.0.0-9.0.16, or 10.0.0-10.0.8.

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.28 / 9.0.17 / 10.0.9 or later
Fixed in 8.0.289.0.1710.0.9
Interim mitigation

Apply Microsoft security patches for .NET when released; follow least-privilege principles for local user accounts and monitor for unusual privilege escalation activity.

Recommended fix High confidence

Upgrade to .NET 8.0.28+, 9.0.17+, or 10.0.9+ depending on your major version branch

  1. Identify the currently installed .NET version by running 'dotnet --version' or checking project file references
  2. For .NET 8.0.x: Upgrade to version 8.0.28 or later
  3. For .NET 9.0.x: Upgrade to version 9.0.17 or later
  4. For .NET 10.0.x: Upgrade to version 10.0.9 or later
  5. Update the runtime or SDK by installing the appropriate version from dotnet.microsoft.com/download or via package manager
  6. Verify the upgrade was successful by running 'dotnet --version'
  7. Rebuild and redeploy any applications using the affected .NET runtime
Caveat Minor version upgrades typically have minimal breaking changes; review release notes for any behavior changes specific to your application

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

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