CVE Tools

CVE-2026-62909

.NET Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 17th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft .NET 10.0Affected: ≥ 10.0.0, < 10.0.11Upgrade to: 10.0.11Stated by: CVE record
  • Microsoft .NET 8.0Affected: ≥ 8.0.0, < 8.0.30Upgrade to: 8.0.30Stated by: CVE record
  • Microsoft .NET 9.0Affected: ≥ 9.0.0, < 9.0.19Upgrade to: 9.0.19Stated by: CVE record
  • Microsoft Visual Studio 2022 version 17.14Affected: ≥ 17.14.0, < 17.14.38Upgrade to: 17.14.38Stated by: CVE record
  • Microsoft Visual Studio 2026 version 18.8Affected: ≥ 18.0, < 18.8.3Upgrade to: 18.8.3Stated by: CVE record

Versions as the sources state them. 3 more products have version data. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run or develop on these installed versions: .NET 8.0, .NET 9.0, .NET 10.0, and Visual Studio 2022 (17.14) or Visual Studio 2026 (18.8).
  2. If your versions are older than the fixed releases below, schedule updates as soon as possible.
  3. Update Visual Studio 2022 to 17.14.38.
  4. Update Visual Studio 2026 to 18.8.3.
  5. Update .NET 8.0 to 8.0.30.
  6. Update .NET 9.0 to 9.0.19.
  7. Update .NET 10.0 to 10.0.11.
  8. After updating, verify the updated versions are in place and that your build/dev workflows still work normally.

What it is

From the CVE record

Uncaught exception in .NET allows an authorized attacker to elevate privileges locally.

In plain language

Written by AI from the record

CVE-2026-62909 is a .NET security flaw that lets a local attacker with low-level access break out of their permissions and take full control of your machine; if you use affected versions of .NET or Visual Studio, you should update now.

CVE-2026-62909 is a local privilege escalation in .NET (CWE-252) where low-privileged access can trigger an unhandled error/exception to gain full system control; it does not require user interaction and is reachable in default configurations.

If you're affected

  • Full workstation takeover
  • Access to sensitive project data
  • Ability to install malware
  • Service disruption on dev machines

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS17th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 17th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 4 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Record updatedrecord updated
  4. Publishedweakness classified, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Visual Studio 2022, not every advisory.