Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-g3q9-xf95-8hp5

HIGH

GHSA-g3q9-xf95-8hp5 is a high-severity (CVSS 7.8) Improper Privilege Management vulnerability in NuGet.Commands. O3 Security confirms whether GHSA-g3q9-xf95-8hp5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NuGet Elevation of Privilege Vulnerability

Also known asBIT-dotnet-2022-41032BIT-dotnet-sdk-2022-41032CVE-2022-41032
Published
Oct 11, 2022
Updated
Feb 28, 2025
Affected
21 pkgs
Patched
21 / 21
Exploits
None indexed

Blast Radius

21 pkgs affected
.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.CommandLine+13 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

Description

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0.0-rc, .NET 6.0, .NET Core 3.1, and NuGet (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A vulnerability exists in .NET 7.0.0-rc.1, .NET 6.0, .NET Core 3.1, and NuGet clients (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol) where a malicious actor could cause a user to execute arbitrary code.

Affected software

NuGet & NuGet Packages

  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 6.3.0 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 6.2.1 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 6.0.2 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 5.11.2 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 5.9.2 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 5.7.2 version or earlier.
  • Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol 4.9.5 version or earlier.

.NET SDK(s)

  • Any .NET 6.0 application running on .NET 6.0.9 or earlier.
  • Any .NET 3.1 application running on .NET Core 3.1.29 or earlier.

Patches

To fix the issue, please install the latest version of .NET 6.0 or .NET Core 3.1 and NuGet (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol versions). If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.

.NET 6.0 and .NET Core 3.1 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.

Other details

Announcement for this issue can be found at https://github.com/NuGet/Announcements/issues/65

MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-41032

Affected Packages

21 total 21 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetNuGet.Commands≥ 4.6.0&&< 4.9.64.9.6
.NETNuGetNuGet.Commands≥ 5.0.0&&< 5.7.35.7.3
.NETNuGetNuGet.Commands≥ 5.8.0&&< 5.9.35.9.3
.NETNuGetNuGet.Commands≥ 5.10.0&&< 5.11.35.11.3
.NETNuGetNuGet.Commands≥ 6.0.0&&< 6.0.36.0.3
.NETNuGetNuGet.Commands≥ 6.1.0&&< 6.2.26.2.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for NuGet.Commands. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update NuGet.Commands to 4.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3q9-xf95-8hp5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-g3q9-xf95-8hp5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g3q9-xf95-8hp5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Description Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0.0-rc, .NET 6.0, .NET Core 3.1, and NuGet (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in .NET 7.0.0-rc.1, .NET 6.0, .NET Core 3.1, and NuGet clients (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol) where a malicious actor could cause a user to execute arbitrary code. ## Affected software ### NuGet &
O3 Security · Impact-Aware SCA

Is GHSA-g3q9-xf95-8hp5 in your dependencies?

O3 detects GHSA-g3q9-xf95-8hp5 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works