NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

CVE-2026-118745 — Microsoft.NETCore.App.Run…

HIGH

CVE-2026-118745 is a high-severity (CVSS 8.8) CWE-122 vulnerability in Microsoft.NETCore.App.Runtime.win-x86. A fix is available for Microsoft.NETCore.App.Runtime.win-x86 — see the affected versions and patch details below.

Microsoft Security Advisory CVE-2026-118745 - Visual Studio Remote Code Execution Vulnerability

Published
Updated
Affected
12 pkgs
Patched
12 / 12
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

12 pkgs affected
.NETMicrosoft.NETCore.App.Runtime.win-x86.NETMicrosoft.NETCore.App.Runtime.win-x64.NETMicrosoft.NETCore.App.Runtime.win-arm64.NETMicrosoft.NETCore.App.Runtime.win-x86.NETMicrosoft.NETCore.App.Runtime.win-x64.NETMicrosoft.NETCore.App.Runtime.win-arm64.NETMicrosoft.NETCore.App.Runtime.win-x86.NETMicrosoft.NETCore.App.Runtime.win-x64+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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.

Crafted PDB line metadata can exceed the caller-provided buffer and cause a heap out-of-bounds write.

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-122

Affected Platforms

  • Platforms: Windows
  • Architectures: x86, x64, Arm64

<a name="affected-packages"></a>Affected Packages

On Windows x86, x64, and Arm64, Microsoft.DiaSymReader.Native versions earlier than 18.9.1-beta1.26515.1 are affected when reading crafted native PDBs.

.NET on Windows

ProductAffected versionPatched version
.NET 8.0 installed on Windows>= 8.0.0, < 8.0.348.0.34
.NET 9.0 installed on Windows>= 9.0.0, < 9.0.239.0.23
.NET 10.0 installed on Windows>= 10.0.0, < 10.0.1510.0.15
.NET 11.0 installed on Windows>= 11.0.0-preview.1, < 11.0.011.0.0

Windows self-contained runtime packs

These runtime packs deliver the .NET runtime for Windows self-contained applications.

PackageAffected versionPatched version
Microsoft.NETCore.App.Runtime.win-x86>= 8.0.0, < 8.0.348.0.34
Microsoft.NETCore.App.Runtime.win-x64>= 8.0.0, < 8.0.348.0.34
Microsoft.NETCore.App.Runtime.win-arm64>= 8.0.0, < 8.0.348.0.34
Microsoft.NETCore.App.Runtime.win-x86>= 9.0.0, < 9.0.239.0.23
Microsoft.NETCore.App.Runtime.win-x64>= 9.0.0, < 9.0.239.0.23
Microsoft.NETCore.App.Runtime.win-arm64>= 9.0.0, < 9.0.239.0.23
Microsoft.NETCore.App.Runtime.win-x86>= 10.0.0, < 10.0.1510.0.15
Microsoft.NETCore.App.Runtime.win-x64>= 10.0.0, < 10.0.1510.0.15
Microsoft.NETCore.App.Runtime.win-arm64>= 10.0.0, < 10.0.1510.0.15
Microsoft.NETCore.App.Runtime.win-x86>= 11.0.0-preview.1, < 11.0.011.0.0
Microsoft.NETCore.App.Runtime.win-x64>= 11.0.0-preview.1, < 11.0.011.0.0
Microsoft.NETCore.App.Runtime.win-arm64>= 11.0.0-preview.1, < 11.0.011.0.0

Windows SDK distributions

These Windows SDK distributions are affected through their bundled .NET runtime.

ProductAffected versionPatched version
.NET SDK 8.0.1xx>= 8.0.100-0, < 8.0.1348.0.134
.NET SDK 8.0.4xx>= 8.0.400-0, < 8.0.4288.0.428
.NET SDK 9.0.1xx>= 9.0.100-0, < 9.0.1249.0.124
.NET SDK 9.0.3xx>= 9.0.300-0, < 9.0.3219.0.321
.NET SDK 10.0.1xx>= 10.0.100-0, < 10.0.11510.0.115
.NET SDK 10.0.4xx>= 10.0.400-0, < 10.0.40410.0.404
.NET SDK 11.0.1xx>= 11.0.100-preview.1, < 11.0.10011.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 on Windows x86, x64, and Arm64 to read crafted native PDBs are exposed. See 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. 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.

Announcement

https://github.com/dotnet/announcements/issues/524

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-118745

Acknowledgements

  • Quac Tran

Revisions

V1.0 (November 10, 2026): Advisory published.

Affected Packages

12 total 12 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x86≥ 8.0.0&&< 8.0.348.0.34dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 8.0.34
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x64≥ 8.0.0&&< 8.0.348.0.34dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 8.0.34
.NETNuGetMicrosoft.NETCore.App.Runtime.win-arm64≥ 8.0.0&&< 8.0.348.0.34dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 8.0.34
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x86≥ 9.0.0&&< 9.0.239.0.23dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 9.0.23
.NETNuGetMicrosoft.NETCore.App.Runtime.win-x64≥ 9.0.0&&< 9.0.239.0.23dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 9.0.23
.NETNuGetMicrosoft.NETCore.App.Runtime.win-arm64≥ 9.0.0&&< 9.0.239.0.23dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 9.0.23

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.App.Runtime.win-x86, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.NETCore.App.Runtime.win-x86 to 8.0.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-118745 is resolved across your whole dependency graph.

  3. Workarounds

    Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

## 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. Crafted PDB line metadata can exceed the caller-provided buffer and cause a heap out-of-bounds write. ## 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-122 ## Affected Platforms - **Platforms:** Windows - **Architectures:** x86, x64, Arm64 ## <a name="affecte
O3 Security · Impact-Aware SCA

Is CVE-2026-118745 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2026-118745: Memory Corruption — Fixed in 8.0.34