## Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET. This advisory provides guidance on updating affected applications and components.
A crafted PDB `LF_DECIMAL` payload can trigger an out-of-bounds stack write when processed by DIA.
## CVSS Details
- **Version:** 3.1
- **Severity:** High
- **Score:** 8.8 (base score)
- **Vector:** `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`
- **Weakness:** CWE-502, CWE-121
## Affected Platforms
- **Platforms:** Windows
- **Architectures:** x86, x64, Arm64
## <a name="affected-packages"></a>Affected Packages
Microsoft.DiaSymReader.Native versions earlier than 18.9.1-beta1.26515.1 are affected when reading constants from attacker-supplied PDBs through `ISymUnmanagedConstant.GetValue`. The .NET runtime's native stack-trace reading path does not call `ISymUnmanagedConstant.GetValue`. This excludes that invocation, not the .NET product as a whole.
### .NET on Windows
Product | Affected version | Patched version
--- | --- | ---
.NET 8.0 installed on Windows | >= 8.0.0, < 8.0.34 | 8.0.34
.NET 9.0 installed on Windows | >= 9.0.0, < 9.0.23 | 9.0.23
.NET 10.0 installed on Windows | >= 10.0.0, < 10.0.15 | 10.0.15
.NET 11.0 installed on Windows | >= 11.0.0-preview.1, < 11.0.0 | 11.0.0
### Windows self-contained runtime packs
These runtime packs deliver the .NET runtime for Windows self-contained applications.
Package | Affected version | Patched version
--- | --- | ---
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 8.0.0, < 8.0.34 | 8.0.34
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 8.0.0, < 8.0.34 | 8.0.34
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 8.0.0, < 8.0.34 | 8.0.34
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 9.0.0, < 9.0.23 | 9.0.23
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 9.0.0, < 9.0.23 | 9.0.23
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 9.0.0, < 9.0.23 | 9.0.23
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 10.0.0, < 10.0.15 | 10.0.15
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 10.0.0, < 10.0.15 | 10.0.15
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 10.0.0, < 10.0.15 | 10.0.15
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 11.0.0-preview.1, < 11.0.0 | 11.0.0
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 11.0.0-preview.1, < 11.0.0 | 11.0.0
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 11.0.0-preview.1, < 11.0.0 | 11.0.0
### Windows SDK distributions
These Windows SDK distributions are affected through their bundled .NET runtime.
Product | Affected version | Patched version
--- | --- | ---
.NET SDK 8.0.1xx | >= 8.0.100-0, < 8.0.134 | 8.0.134
.NET SDK 8.0.4xx | >= 8.0.400-0, < 8.0.428 | 8.0.428
.NET SDK 9.0.1xx | >= 9.0.100-0, < 9.0.124 | 9.0.124
.NET SDK 9.0.3xx | >= 9.0.300-0, < 9.0.321 | 9.0.321
.NET SDK 10.0.1xx | >= 10.0.100-0, < 10.0.115 | 10.0.115
.NET SDK 10.0.4xx | >= 10.0.400-0, < 10.0.404 | 10.0.404
.NET SDK 11.0.1xx | >= 11.0.100-preview.1, < 11.0.100 | 11.0.100
### Windows SDK updates
Update each installed SDK feature band to the following version or later:
- .NET SDK 8.0.1xx: 8.0.134
- .NET SDK 8.0.4xx: 8.0.428
- .NET SDK 9.0.1xx: 9.0.124
- .NET SDK 9.0.3xx: 9.0.321
- .NET SDK 10.0.1xx: 10.0.115
- .NET SDK 10.0.4xx: 10.0.404
- .NET SDK 11.0.1xx: 11.0.100
## Advisory FAQ
### <a name="how-affected"></a>How do I know if I am affected?
Applications using Microsoft.DiaSymReader.Native versions earlier than 18.9.1-beta1.26515.1 to read constants from attacker-supplied PDBs through `ISymUnmanagedConstant.GetValue` are exposed on x86, x64, and Arm64. The .NET runtime's native stack-trace reading path does not call `ISymUnmanagedConstant.GetValue`. This excludes that invocation, not the .NET product as a whole. See [affected packages](#affected-packages) for the affected .NET products on Windows.
### <a name="how-fix"></a>How do I fix the issue?
Update affected .NET installations and each installed SDK feature band to the versions listed above or later. If an SDK was installed through Visual Studio, update Visual Studio as well.
Microsoft.DiaSymReader.Native is delivered through .NET Core rather than as a standalone customer NuGet update. For applications that deploy their own affected .NET runtime, including self-contained applications, update the runtime used to build the application, rebuild, and redeploy. Updating a machine-wide runtime does not replace an application's embedded runtime. Restart processes that have loaded the affected native reader.
## 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](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue).
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-114151](https://www.cve.org/CVERecord?id=CVE-2026-114151)
### Acknowledgements
- 41ae55e9310ff27fa6f26af4727e5590
### Revisions
V1.0 (November 10, 2026): Advisory published.
## Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-fpxj-5c99-g7vj. This link is maintained to preserve external references.
## Original Description
Deserialization of untrusted data in Visual Studio allows an unauthorized attacker to execute code over a network.
CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
CVE-2026-114151
This is a saved version of the risk data. The advisory details have their own history. Latest risk data.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.49 % · percentile 74.56 % · scored 14 Nov 2026. This score is more than two days old.
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
How advisory history works
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.