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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · 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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 Portable PDB `EmbeddedSource` record with parent RID 0 can trigger an 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

Affected Packages Microsoft.DiaSymReader.Native components bundled with the affected .NET versions listed below are affected when initializing the native reader with a crafted Portable PDB containing an `EmbeddedSource` record with parent RID 0. The Windows runtime's native stack-trace reader can reach this initialization through its native-reader fallback.

.NET on Windows Product | Affected version | Patched version --- |…

Published by the source

11 Nov 2026, 00:34 UTC

Last modified by the source

11 Nov 2026, 00:45 UTC

Source last checked

11 Nov 2026, 07:35 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-r8h3-p8p6-ggp7

2. Revision 1 · created · 11 Nov 2026

   Published from ghsa record GHSA-r8h3-p8p6-ggp7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114158

Advisory: Microsoft Security Advisory CVE-2026-114158 - Visual Studio Remote Code Execution Vulnerability
IDs: CVE-2026-114158, GHSA-r8h3-p8p6-ggp7
Record: https://patchnext.com/advisories/cve-2026-114158 (revision 2, source checked 11 Nov 2026, 07:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.netcore.app.runtime.win-x86 11.0.0, 10.0.15, 9.0.23, 8.0.34; microsoft.netcore.app.runtime.win-arm64 11.0.0, 10.0.15, 9.0.23, 8.0.34; microsoft.netcore.app.runtime.win-x64 11.0.0, 10.0.15, 9.0.23, 8.0.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.netcore.app.runtime.win-x86: affected >= 8.0.0, < 8.0.34; >= 9.0.0, < 9.0.23; >= 10.0.0, < 10.0.15; >= 11.0.0-preview.1, < 11.0.0; fixed in 9.0.23, 8.0.34, 10.0.15, 11.0.0
- NuGet microsoft.netcore.app.runtime.win-arm64: affected >= 8.0.0, < 8.0.34; >= 9.0.0, < 9.0.23; >= 10.0.0, < 10.0.15; >= 11.0.0-preview.1, < 11.0.0; fixed in 9.0.23, 8.0.34, 10.0.15, 11.0.0
- NuGet microsoft.netcore.app.runtime.win-x64: affected >= 8.0.0, < 8.0.34; >= 9.0.0, < 9.0.23; >= 10.0.0, < 10.0.15; >= 11.0.0-preview.1, < 11.0.0; fixed in 9.0.23, 8.0.34, 10.0.15, 11.0.0

## Suggested inspection (read-only)
- NuGet microsoft.netcore.app.runtime.win-x86: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-arm64: check the installed version with your package manager.
- NuGet microsoft.netcore.app.runtime.win-x64: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.netcore.app.runtime.win-x86, microsoft.netcore.app.runtime.win-arm64, microsoft.netcore.app.runtime.win-x64.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r8h3-p8p6-ggp7 (GitHub-reviewed advisory GHSA-r8h3-p8p6-ggp7 lists affected ranges: NuGet microsoft.netcore.app.runtime.win-x86 >=8.0.0 =9.0.0 =10.0.0 =11.0.0-preview.1 =8.0.0 =9.0.0 =10.0.0 =11.0.0-preview.1 =8.0.0 =9.0.0 =10.0.0 =11.0.0-preview.1 <11.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-r8h3-p8p6-ggp7 (OSV record GHSA-r8h3-p8p6-ggp7 lists affected ranges: NuGet microsoft.netcore.app.runtime.win-x86 >=8.0.0 =9.0.0 =10.0.0 =11.0.0-preview.1 =8.0.0 =9.0.0 =10.0.0 =11.0.0-preview.1 =8.0.0 =9.0.0 =10.0.0 <10.0.15 (fixed),…)

Commands are suggestions: review each one before running it.