Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-crjq-wm6x-6qx7

HighCVSS 7.8 / 10
Published Mar 11, 2026·Last modified Apr 6, 2026
Affected Components(0)

No affected components available

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.

Risk Scores
Base Score
7.8

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.

Threat Intelligence
7.1

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard