Microsoft Security Advisory CVE-2026-26127 – .NET Denial of Service Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 9.0 and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A denial of service vulnerability exists in .NET and Microsoft.Bcl.Memory due to an out-of-bounds read when decoding malformed Base64Url input.
Announcement
Announcement for this issue can be found at dotnet/announcements#384
CVSS Details
- Version: 3.1
- Score: 7.5
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
- Severity: High
- Weakness: CWE-129 (Improper Validation of Array Index); CWE-125 (Out-of-bounds Read)
Affected Platforms
- Platforms: All
- Architectures: All
Affected Products
.NET 9
| Package name |
Affected version |
Patched version |
| Microsoft.NetCore.App.Runtime.linux-arm |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.linux-arm64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.linux-musl-x64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.linux-x64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.osx-arm64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.osx-x64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.win-arm |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.win-arm64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.win-x64 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
| Microsoft.NetCore.App.Runtime.win-x86 |
>= 9.0.0, <= 9.0.13 |
9.0.14 |
.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 |
| Microsoft.NetCore.App.Runtime.osx-arm64 |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
| Microsoft.NetCore.App.Runtime.osx-x64 |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
| Microsoft.NetCore.App.Runtime.win-arm |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
| Microsoft.NetCore.App.Runtime.win-arm64 |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
| Microsoft.NetCore.App.Runtime.win-x64 |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
| Microsoft.NetCore.App.Runtime.win-x86 |
>= 10.0.0, <= 10.0.3 |
10.0.4 |
Micorsoft.Bcl.Memory 9.0.14
Micorsoft.Bcl.Memory 10.0.4
How do I fix the issue?
To update the Microsoft.Bcl.Memory NuGet package, use one of the following methods:
NuGet Package Manager UI in Visual Studio:
- Open your project in Visual Studio.
- Right-click on your project in Solution Explorer and select "Manage NuGet Packages..." or navigate to "Project > Manage NuGet Packages".
- In the NuGet Package Manager window, select the "Updates" tab. This tab lists packages with available updates from your configured package sources.
- Select the package(s) you wish to update. You can choose a specific version from the dropdown or update to the latest available version.
- Click the "Update" button.
Using the NuGet Package Manager Console in Visual Studio:
- Open your project in Visual Studio.
- Navigate to "Tools > NuGet Package Manager > Package Manager Console".
- To update a specific package to its latest version, use the following Update-Package command:
Update-Package -Id Microsoft.Bcl.Memory
Using the .NET CLI (Command Line Interface):
- Open a terminal or command prompt in your project's directory.
- To update a specific package to its latest version, use the following add package command:
dotnet package update Microsoft.Bcl.Memory
Once you have updated the nuget package reference you must recompile and deploy your application. Additionally we recommend you update your runtime and/or SDKs, but unless you are targeting .NET 9 or higher, updating your runtime and/or SDK is not a required step to patch this vulnerability.
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-26127
Revisions
V1.0 (March 10, 2026): Advisory published.
Microsoft Security Advisory CVE-2026-26127 – .NET Denial of Service Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 9.0 and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A denial of service vulnerability exists in .NET and Microsoft.Bcl.Memory due to an out-of-bounds read when decoding malformed Base64Url input.
Announcement
Announcement for this issue can be found at dotnet/announcements#384
CVSS Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:CAffected Platforms
Affected Products
.NET 9
.NET 10
Micorsoft.Bcl.Memory 9.0.14
Micorsoft.Bcl.Memory 10.0.4
How do I fix the issue?
To update the Microsoft.Bcl.Memory NuGet package, use one of the following methods:
NuGet Package Manager UI in Visual Studio:
Using the NuGet Package Manager Console in Visual Studio:
Update-Package -Id Microsoft.Bcl.MemoryUsing the .NET CLI (Command Line Interface):
dotnet package update Microsoft.Bcl.MemoryOnce you have updated the nuget package reference you must recompile and deploy your application. Additionally we recommend you update your runtime and/or SDKs, but unless you are targeting .NET 9 or higher, updating your runtime and/or SDK is not a required step to patch this vulnerability.
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-26127
Revisions
V1.0 (March 10, 2026): Advisory published.