Skip to content

← Actionable
High, CVSS 7.8

Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability

CVE-2023-36792GHSA-3qf9-qxfj-4whc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.netcore.app.runtime.win-x86 7.0.11, 6.0.22; microsoft.netcore.app.runtime.win-arm64 7.0.11, 6.0.22; microsoft.netcore.app.runtime.win-x64 7.0.11, 6.0.22), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-3qf9-qxfj-4whc lists affected ranges: NuGet microsoft.netcore.app.runtime.win-arm64 >=7.0.0 =6.0.0 =7.0.0 =6.0.0 =6.0.0 =7.0.0 <=7.0.10

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2023-36792: 1.23% estimated exploitation activity in the next 30 days; percentile 68.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability <a name="executive-summary"</aExecutive summary Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Microsoft.DiaSymReader.Native.amd64.dll when reading a corrupted PDB file which may lead to remote code execution. This issue only affects Windows systems. Note: The vulnerabilities CVE-2023-36792, CVE-2023-36793, CVE-2023-36792, CVE-2023-36796 are all resolved by a single patch. Get affected software to resolve all of them. Discussion Discussion for this issue can be found at https://github.com/dotnet/runtime/issues/91944 <a name="mitigation-factors"</aMitigation factors Microsoft has not identified any mitigating factors for this vulnerability. <a name="affected-software"</aAffected software…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3qf9-qxfj-4whc

Agent brief

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

# Patch Next advisory brief: CVE-2023-36792

Advisory: Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability
IDs: CVE-2023-36792, GHSA-3qf9-qxfj-4whc
Record: https://patchnext.com/advisories/cve-2023-36792 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.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 7.0.11, 6.0.22; microsoft.netcore.app.runtime.win-arm64 7.0.11, 6.0.22; microsoft.netcore.app.runtime.win-x64 7.0.11, 6.0.22. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.netcore.app.runtime.win-x86: affected >= 6.0.0, <= 6.0.21; >= 7.0.0, <= 7.0.10; fixed in 6.0.22, 7.0.11
- NuGet microsoft.netcore.app.runtime.win-arm64: affected >= 7.0.0, <= 7.0.10; >= 6.0.0, <= 6.0.21; fixed in 6.0.22, 7.0.11
- NuGet microsoft.netcore.app.runtime.win-x64: affected >= 7.0.0, <= 7.0.10; >= 6.0.0, <= 6.0.21; fixed in 6.0.22, 7.0.11

## 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-3qf9-qxfj-4whc (GitHub-reviewed advisory GHSA-3qf9-qxfj-4whc lists affected ranges: NuGet microsoft.netcore.app.runtime.win-arm64 >=7.0.0 =6.0.0 =7.0.0 =6.0.0 =6.0.0 =7.0.0 <=7.0.10)

Commands are suggestions: review each one before running it.

Loading voting…