Skip to content

GHSA-crjq-wm6x-6qx7 BIT-dotnet-2026-26131 BIT-dotnet-sdk-2026-26131 CVE-2026-26131

.NET Elevation of Privilege Vulnerability

High NuGet
Severity
7.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.37%
Chance of exploitation in the next 30 days. Higher than 31.36% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-276 Incorrect Default Permissions
Fix
Available
6 packages have a fixed version

Description

Microsoft Security Advisory CVE-2026-26131 – .NET Elevation of Privilege Vulnerability

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

An elevation of privilege vulnerability exists in .NET due to improper authorization. Incorrect packaging permissions could allow an attacker to gain elevated privileges.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/386

CVSS Details

  • Severity: High
  • Version: 3.1
  • Score: 7.8
  • 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
  • Weakness: CWE-276 (Incorrect Default Permissions)

Affected Platforms

  • Platforms: Linux
  • Architectures: All

Affected Products

<a name=".NET 10"></a>.NET 10
Package name Affected version Patched version
Microsoft.NetCore.App.Runtime.linux-arm >= 10.0.0, <= 10.0.3 10.0.4
Microsoft.NetCore.App.Runtime.linux-arm64 >= 10.0.0, <= 10.0.3 10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-arm >= 10.0.0, <= 10.0.3 10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-arm64 >= 10.0.0, <= 10.0.3 10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-x64 >= 10.0.0, <= 10.0.3 10.0.4
Microsoft.NetCore.App.Runtime.linux-x64 >= 10.0.0, <= 10.0.3 10.0.4

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

If using an affected package listed in affected products, you're exposed to the vulnerability.

<a name="how-fix"></a>How do I fix the issue?
  1. To fix the issue please install the latest version of .NET 10.0. 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.
  2. 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 --info command.

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

CVE-2026-26131

Acknowledgements

Igor Kovalchuk

Revisions

V1.0 (March 10, 2026): Advisory published.

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.NetCore.App.Runtime.linux-arm
>= 10.0.0, < 10.0.4
10.0.4
Microsoft.NetCore.App.Runtime.linux-arm64
>= 10.0.0, < 10.0.4
10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-arm
>= 10.0.0, < 10.0.4
10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-arm64
>= 10.0.0, < 10.0.4
10.0.4
Microsoft.NetCore.App.Runtime.linux-musl-x64
>= 10.0.0, < 10.0.4
10.0.4
Microsoft.NetCore.App.Runtime.linux-x64
>= 10.0.0, < 10.0.4
10.0.4

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 → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-arm --version 10.0.4

Microsoft.NetCore.App.Runtime.linux-arm64 NuGet → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-arm64 --version 10.0.4

Microsoft.NetCore.App.Runtime.linux-musl-arm NuGet → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-arm --version 10.0.4

Microsoft.NetCore.App.Runtime.linux-musl-arm64 NuGet → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-arm64 --version 10.0.4

Microsoft.NetCore.App.Runtime.linux-musl-x64 NuGet → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-x64 --version 10.0.4

Microsoft.NetCore.App.Runtime.linux-x64 NuGet → 10.0.4

dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-x64 --version 10.0.4

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-276: Incorrect Default Permissions

During installation, installed file permissions are set to allow anyone to modify those files.

How to prevent it
  • Architecture and Design, Operation: The architecture needs to access and modification attributes for files to only those users who actually require those actions.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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-2j93-m82w-73j2
Microsoft Security Advisory CVE-2026-96231 - .NET and Visual Studio Elevation of Privilege 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
Is this in your code?

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