GHSA-2j93-m82w-73j2 CVE-2026-96231
Microsoft Security Advisory CVE-2026-96231 - .NET and Visual Studio Elevation of Privilege Vulnerability
- Severity
- 7.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.41%
- Chance of exploitation in the next 30 days. Higher than 35.34% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-59 Improper Link Resolution Before File Access ('Link Following')
- Fix
- Available
- 8 packages have a fixed version
Description
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.NETCore.App.Runtime; System.Private.CoreLib. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Unix named-mutex and shared-memory paths can be manipulated through insecure global directories, symlink races, and unsafe permission changes, allowing local attackers to truncate or overwrite files, widen directory permissions, or elevate privileges.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/479
CVSS Details
- Version: 3.1
- Severity: High
- Score: 7.8
- Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness: CWE-59 (Improper Link Resolution Before File Access ('Link Following'))
Affected Platforms
- Platforms: Linux, macOS
- Architectures: All
<a name="affected-packages"></a>Affected Packages
The vulnerability affects Microsoft .NET projects that use an affected package version listed below.
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If using a package listed in affected packages, you're exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
- To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
- If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the
dotnet --infocommand.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Acknowledgements
- Nguyễn Văn Minh Đức with Saigon Newport Corporation
Revisions
V1.0 (10/13/2026): Advisory published.
Affected versions
NuGet
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
Microsoft.NETCore.App.Runtime.linux-arm NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm --version 8.0.32
Microsoft.NETCore.App.Runtime.linux-arm64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm64 --version 8.0.32
Microsoft.NETCore.App.Runtime.linux-musl-arm NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm --version 8.0.32
Microsoft.NETCore.App.Runtime.linux-musl-arm64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm64 --version 8.0.32
Microsoft.NETCore.App.Runtime.linux-musl-x64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-x64 --version 8.0.32
Microsoft.NETCore.App.Runtime.linux-x64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-x64 --version 8.0.32
Microsoft.NETCore.App.Runtime.osx-arm64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-arm64 --version 8.0.32
Microsoft.NETCore.App.Runtime.osx-x64 NuGet → 8.0.32
- dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-x64 --version 8.0.32
Severity breakdown
CVSS 3.1 7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-59: Improper Link Resolution Before File Access ('Link Following')
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
How to prevent it
- Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
References
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2020-1147 .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability | High Known exploited | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-87vj-4hqv-22p9 Microsoft Security Advisory CVE-2026-96233 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-w6wh-p4g7-mpj2 Microsoft Security Advisory CVE-2026-96225 - .NET and Visual Studio Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-fqpq-cx42-9jmm Microsoft Security Advisory CVE-2026-70194 - .NET and Visual Studio Security Feature Bypass Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-3rxq-g8rj-r2cf Microsoft Security Advisory CVE-2026-69651 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-wxxw-5cvc-53j7 Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-mc4q-93x5-f6hj Microsoft Security Advisory CVE-2026-58280 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-9mr8-pwpw-3j2w Microsoft Security Advisory CVE-2026-62909 – .NET Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor