.NET Remote Code Execution Vulnerability

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-35390: 2.08% estimated exploitation activity in the next 30 days; percentile 81.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Microsoft Security Advisory CVE-2023-35390: .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 when some dotnet commands are used in directories with weaker permissions which can result in remote code execution. Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/266 <a name="mitigation-factors"</aMitigation factors Microsoft has not identified any mitigating factors for this vulnerability. <a name="affected-software"</aAffected software Any .NET 7.0.1xx SDK 7.0.109 or earlier. Any .NET 7.0.3xx SDK 7.0.306 or earlier. Any .NET 6.0.1xx SDK 6.0.120 or earlier. Any .NET 6.0.3xx SDK 6.0.315 or earlier. Any .NET 6.0.4xx SDK 6.0.412 or earlier.…

Published by the source

9 Aug 2023, 13:15 UTC

Last modified by the source

3 Jun 2024, 18:31 UTC

Source last checked

26 Oct 2026, 17:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p8rx-fwgq-rh2f

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

# Patch Next advisory brief: CVE-2023-35390

Advisory: .NET Remote Code Execution Vulnerability
IDs: CVE-2023-35390, GHSA-p8rx-fwgq-rh2f
Record: https://patchnext.com/advisories/cve-2023-35390 (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.net.build.containers 7.0.307. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.net.build.containers: affected <= 7.0.306; fixed in 7.0.307

## Suggested inspection (read-only)
- NuGet microsoft.net.build.containers: 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.net.build.containers.
- 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-p8rx-fwgq-rh2f (GitHub-reviewed advisory GHSA-p8rx-fwgq-rh2f lists affected ranges: NuGet microsoft.net.build.containers >=0 <=7.0.306)

Commands are suggestions: review each one before running it.