CVE-2026-114152
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
.NET is a free, open-source, cross-platform framework for building modern apps and powerful cloud services. It consists of a runtime and a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
A remote code execution vulnerability (CVE-2026-114152) has been identified in Microsoft.DiaSymReader.Native, the native symbol reader that the .NET shared framework carries on Windows. Microsoft describes the issue as an out-of-bounds stack write that attacker-controlled COFF relocation offsets can cause. HeroDevs investigation traced the .NET 6 exposure to the runtime's MicrosoftDiaSymReaderNativeVersion pin, which stayed below the fixed build through NES for .NET 6.0.48.
Per CWE-121: Stack-based Buffer Overflow, the weakness is a buffer overflow in which the buffer that is overwritten is allocated on the stack. Microsoft also assigns CWE-822: Untrusted Pointer Dereference.
Every .NET 6 release up to and including NES for .NET 6.0.48 carries an affected version of the component. It ships in-box in the Microsoft.NETCore.App shared framework rather than as an opt-in package, and it is Windows-only, so Linux and macOS layouts do not carry it at all. Exploitation requires user interaction: something must load a crafted PDB that references an attacker-influenced COFF object. Microsoft fixed the issue in its November 10, 2026 releases of .NET 8.0, 9.0, 10.0 and 11.0. 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.
Details
Module Info
- Product: .NET
- Affected packages:
Microsoft.DiaSymReader.Native(in-box in the WindowsMicrosoft.NETCore.Appshared framework and itsMicrosoft.NETCore.App.Runtime.win-*runtime packs, not an opt-in package) - Affected versions:
>=6.0.0 <=6.0.48Microsoft.DiaSymReader.Native < 18.9.1-beta1.26515.1
- Package manager: NuGet, Windows Installer, Docker
- GitHub repository: https://github.com/dotnet/runtime
- Published packages: Download .NET, Microsoft.DiaSymReader.Native on NuGet
- Fixed in: NES for .NET 6.0.49 (SDK 6.0.440)
Vulnerability Info
This High-severity vulnerability is found in the native symbol reader carried by the Microsoft.NETCore.App shared framework on Windows, in versions of Microsoft.DiaSymReader.Native before 18.9.1-beta1.26515.1.
COFF is the object-file format produced by the Microsoft C and C++ toolchain, and a PDB can reference the object files it was built from. When a caller loads document information from such a PDB, the reader can open the referenced object and apply its relocations, each of which names an offset where an address must be patched. Microsoft states that attacker-controlled relocation offsets can cause an out-of-bounds stack write in DiaObjectFile::ApplyFixup. Microsoft's second weakness, CWE-822, fits that shape: an offset read from the file decides where the reader writes. Because the attacker controls the object file, the attacker influences the overwrite.
CVE-2026-114151, CVE-2026-114152, CVE-2026-118745, CVE-2026-114158 and CVE-2026-114159 were reported separately and are addressed together by the single Microsoft.DiaSymReader.Native update to 18.9.1-beta1.26515.1 in NES for .NET 6.0.49.
The advisory's lower bound is open (< 18.9.1-beta1.26515.1), so the weakness is present in every .NET 6 release before NES for .NET 6.0.49 and likely earlier.
Mitigation
.NET 6 is End-of-Life and will not receive any updates to address this issue. For more information see .NET and .NET Core official support policy.
Users of the affected components should apply one of the following mitigations:
- Upgrade affected applications to one of: .NET Runtime >=10.0.15, .NET Runtime >=11.0.0. .NET 8.0.34 and 9.0.23 are fixed but End-of-Life.
- Leverage a commercial support partner like HeroDevs for post-EOL security support, including NES for .NET 6.0.49 or later.
Credits
Microsoft's security advisory acknowledges C0rk1, along with a second reporter listed only under an opaque identifier.