Abstract illustration of connected devices separated by a protected security boundary.
Microsoft’s CVE-2026-96225, titled “.NET Elevation of Privilege Vulnerability,” addresses a local privilege-escalation flaw that could let an authorized attacker gain ROOT privileges. Microsoft rates the vulnerability Important, with a CVSS base score of 7.8. The affected-product list covers .NET runtimes on Linux and Mac OS, plus two Visual Studio release branches.

For administrators and development teams, the practical takeaway is to check both runtime deployments and development tools. The advisory provides separate fixed builds for those products: updating one entry should not be treated as evidence that every affected installation has been remediated.

Abstract illustration of connected devices separated by a protected security boundary. What the vulnerability allows​

According to Microsoft’s security advisory, improper link resolution before file access—also called “link following”—in .NET allows an authorized attacker to elevate privileges locally. Microsoft identifies the weakness as CWE-59 and explicitly states that successful exploitation could grant ROOT privileges.

The local-access requirement matters. This is not described as an unauthenticated remote attack: the supplied CVSS vector specifies local access and low privileges. However, the potential outcome is substantial, with high impacts to confidentiality, integrity, and availability.

Microsoft’s advisory records the following assessment:

FieldMicrosoft’s assessment
CVECVE-2026-96225
Exact title.NET Elevation of Privilege Vulnerability
SeverityImportant
CVSS base score7.8
CVSS temporal score6.8
WeaknessCWE-59
Exploitation assessmentExploitation Less Likely

CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

  • Publicly disclosed: No
  • Exploited: No
  • Customer action required: Yes

Read together, the vector’s local access, low attack complexity, low privileges, and no user-interaction requirements describe a flaw that needs an existing foothold but not another user’s participation. Its scope is unchanged, while all three principal impact categories are rated high.

“Exploitation Less Likely” is a prioritization assessment, not a reason to leave affected installations unpatched. Microsoft’s customer-action status remains explicit.

Affected products and exact remediation​

Microsoft’s affected-product information maps the runtime fixes to three KB articles and a separate release-candidate fixed build. The Visual Studio release information supplies the fixed build for each listed development-tool branch.

The following preserves the product-specific remediation instructions and their exact KB-to-build mappings.

.NET 10.0 runtimes​

  • For .NET 10.0 runtime installed on Linux, install KB5130036 to reach fixed build 10.0.13.
  • For .NET 10.0 runtime installed on Mac OS, install KB5130036 to reach fixed build 10.0.13.

.NET 11.0 runtimes​

  • For .NET 11.0 runtime installed on Linux, update to fixed build 11.0.0-rc.2 or later.
  • For .NET 11.0 runtime installed on Mac OS, update to fixed build 11.0.0-rc.2 or later.

.NET 8.0 runtimes​

  • For .NET 8.0 runtime installed on Linux, install KB5130034 to reach fixed build 8.0.32.
  • For .NET 8.0 runtime installed on Mac OS, install KB5130034 to reach fixed build 8.0.32.

.NET 9.0 runtimes​

  • For .NET 9.0 runtime installed on Linux, install KB5130035 to reach fixed build 9.0.21.
  • For .NET 9.0 runtime installed on Mac OS, install KB5130035 to reach fixed build 9.0.21.

Visual Studio​

  • For Microsoft Visual Studio 2022 version 17.14, update to fixed build 17.14.42 or later.
  • For Microsoft Visual Studio 2026 version 18.10, update to fixed build 18.10.4 or later.

The important comparison is that Linux and Mac OS share the same fixed-build target within each listed runtime branch, while the two Visual Studio branches have their own targets. There is no single version number that serves as a completion check across this entire advisory.

Turn the advisory into a patch-verification checklist​

The following operational guidance is derived from Microsoft’s affected-product mappings and attack assessment, rather than an additional claim about exploitation.

  1. Inventory by product and branch. Match each affected installation to its exact entry above. Keep runtime installations and Visual Studio installations as separate checklist items.
  2. Apply the corresponding remediation. Use the KB-to-build mapping or the specified fixed-build target for that entry. Do not substitute a fix from another branch.
  3. Verify the installed build after updating. Record the resulting version against the relevant target, rather than closing the task solely because an update was initiated.
  4. Prioritize with the local attack requirement in mind. Systems where lower-privileged users have access deserve particular attention because the advisory describes an authorized, local attacker gaining elevated privileges.

For example, a team using Microsoft Visual Studio 2022 version 17.14 alongside a .NET 10.0 runtime installed on Linux has two distinct remediation checks: 17.14.42 or later for the development tool, and KB5130036 → 10.0.13 for the runtime. Completing either check does not establish completion of the other.

The bottom line: CVE-2026-96225 warrants a coordinated runtime-and-tooling patch review. Microsoft’s assessment indicates exploitation is less likely, but the potential gain of ROOT privileges makes verifying the correct fixed build—not merely scheduling an update—the meaningful finish line.

 

References

  1. Official MSRC or vendor evidence api.msrc.microsoft.com
  2. Official MSRC or vendor evidence msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com