7.5
High
Microsoft.Bcl.Memory

CVE-2026-26127

CVE-2026-26127 is a high-severity out-of-bounds read vulnerability in Microsoft.Bcl.Memory (nuget), affecting versions >= 9.0.0, <= 9.0.13. It is fixed in 9.0.14, 10.0.4.

Key facts
CVSS score
7.5
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
Microsoft.Bcl.Memory
Fixed in
9.0.14, 10.0.4
Disclosed
2026

Summary

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 https://github.com/dotnet/announcements/issues/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 <a name=".NET 9"></a>.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 <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 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 <a name="Microsoft.Bcl.Memory 9.0.14"></a>Microsoft.Bcl.Memory 9.0.14 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.Bcl.Memory | >= 9.0.0, <= 9.0.13 | 9.0.14 <a name="Microsoft.Bcl.Memory 10.0.4"></a>Microsoft.Bcl.Memory 10.0.4 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.Bcl.Memory | >= 10.0.0, <= 10.0.3 | 10.0.4 <a name="how-fix"></a>How to fix the issue To update the Microsoft.Bcl.Memory NuGet package, apply one of the following methods: NuGet Package Manager UI in Visual Studio: Open the project in Visual Studio. Right-click on the 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 the configured package sources. Select the package(s) to update. A specific version can be chosen from the dropdown, or the latest available version can be selected. Click the "Update" button. Using the NuGet Package Manager Console in Visual Studio: Open the project in Visual Studio. Navigate to "Tools > NuGet Package Manager > Package Manager Console". To update a specific package to its latest version, run the following Update-Package command: Using the .NET CLI (Command Line Interface): Open a terminal or command prompt in the project's directory. To update a specific package to its latest version, run the following command: Once the NuGet package reference has been updated, the application must be recompiled and redeployed. Additionally, it is recommended to update the runtime and/or SDKs, but unless the application targets .NET 9 or higher, updating the runtime and/or SDK is not a required step to patch this vulnerability. Other Information Reporting Security Issues If a potential security issue has been found in a supported version of .NET, it should be reported 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 Questions about this issue can be asked 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. Questions can be asked 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.

Impact

What is out-of-bounds read?

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Severity and exposure

CVE-2026-26127 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (9.0.14, 10.0.4). Upgrading removes the vulnerable code path.

Affected versions

nuget

  • Microsoft.Bcl.Memory (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-arm (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-arm64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-x64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-x64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.osx-arm64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.osx-x64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-arm (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-arm64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-x64 (>= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-x86 (>= 9.0.0, <= 9.0.13)
  • Microsoft.Bcl.Memory (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-arm (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-arm64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-musl-x64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.linux-x64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.osx-arm64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.osx-x64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.win-arm (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.win-x64 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.win-x86 (>= 10.0.0, <= 10.0.3)
  • Microsoft.NetCore.App.Runtime.win-arm64 (>= 10.0.0, <= 10.0.3)

Security releases

  • Microsoft.Bcl.Memory → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-arm → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-arm64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-x64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-x64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.osx-arm64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.osx-x64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.win-arm → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.win-arm64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.win-x64 → 9.0.14 (nuget)
  • Microsoft.NetCore.App.Runtime.win-x86 → 9.0.14 (nuget)
  • Microsoft.Bcl.Memory → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-arm → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-arm64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-musl-x64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.linux-x64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.osx-arm64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.osx-x64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.win-arm → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.win-x64 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.win-x86 → 10.0.4 (nuget)
  • Microsoft.NetCore.App.Runtime.win-arm64 → 10.0.4 (nuget)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-26127 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-26127 is reachable in your applications. Get a demo

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade Microsoft.Bcl.Memory to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x86 to 9.0.14 or later
  • Upgrade Microsoft.Bcl.Memory to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x86 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm64 to 10.0.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-26127

What is CVE-2026-26127?

CVE-2026-26127 is a high-severity out-of-bounds read vulnerability in Microsoft.Bcl.Memory (nuget), affecting versions >= 9.0.0, <= 9.0.13. It is fixed in 9.0.14, 10.0.4. A read operation accesses a memory location beyond the intended buffer boundary.

How severe is CVE-2026-26127?

CVE-2026-26127 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2026-26127?
  • Microsoft.Bcl.Memory (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-arm (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-arm64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-arm64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-musl-x64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.linux-x64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.osx-arm64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.osx-x64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-arm (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-arm64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-x64 (nuget) (versions >= 9.0.0, <= 9.0.13)
  • Microsoft.NetCore.App.Runtime.win-x86 (nuget) (versions >= 9.0.0, <= 9.0.13)
Is there a fix for CVE-2026-26127?

Yes. CVE-2026-26127 is fixed in 9.0.14, 10.0.4. Upgrade to this version or later.

Is CVE-2026-26127 exploitable, and should I be worried?

Whether CVE-2026-26127 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-26127 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-26127?
  • Upgrade Microsoft.Bcl.Memory to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x64 to 9.0.14 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x86 to 9.0.14 or later
  • Upgrade Microsoft.Bcl.Memory to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-musl-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.linux-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-arm64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.osx-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x64 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-x86 to 10.0.4 or later
  • Upgrade Microsoft.NetCore.App.Runtime.win-arm64 to 10.0.4 or later

Stop the waste.
Protect your environment with Kodem.