Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

GHSA-g3q9-xf95-8hp5 NuGet.Commands

HIGHFix: NuGet/NuGet.Client@6392863

GHSA-g3q9-xf95-8hp5 is a high-severity (CVSS 7.8) Improper Privilege Management vulnerability in NuGet.Commands. A fix is available for NuGet.Commands — see the affected versions and patch details below.

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
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g3q9-xf95-8hp5.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-g3q9-xf95-8hp5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

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.Commands4.6.0&&< 4.9.64.9.6dotnet add package NuGet.Commands --version 4.9.6
.NETNuGetNuGet.Commands5.0.0&&< 5.7.35.7.3dotnet add package NuGet.Commands --version 5.7.3
.NETNuGetNuGet.Commands5.8.0&&< 5.9.35.9.3dotnet add package NuGet.Commands --version 5.9.3
.NETNuGetNuGet.Commands5.10.0&&< 5.11.35.11.3dotnet add package NuGet.Commands --version 5.11.3
.NETNuGetNuGet.Commands6.0.0&&< 6.0.36.0.3dotnet add package NuGet.Commands --version 6.0.3
.NETNuGetNuGet.Commands6.1.0&&< 6.2.26.2.2dotnet add package NuGet.Commands --version 6.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g3q9-xf95-8hp5 can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
.NET Core on Red Hat Enterprise Linuxrh-dotnet31-dotnet-0:3.1.424-1.el7_9RHSA-2022:6914
.NET Core on Red Hat Enterprise Linuxrh-dotnet60-dotnet-0:6.0.110-1.el7_9RHSA-2022:6915
Red Hat Enterprise Linux 8dotnet6.0-0:6.0.110-1.el8_6RHSA-2022:6911
Red Hat Enterprise Linux 8dotnet3.1-0:3.1.424-1.el8_6RHSA-2022:6912
Red Hat Enterprise Linux 8dotnet7.0-0:7.0.100-0.4.rc2.el8_7RHSA-2022:7826
Red Hat Enterprise Linux 9dotnet6.0-0:6.0.110-1.el9_0RHSA-2022:6913
Red Hat Enterprise Linux 9dotnet7.0-0:7.0.100-0.5.rc2.el9_1RHSA-2022:8434

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 Security finds GHSA-g3q9-xf95-8hp5 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-g3q9-xf95-8hp5: RCE (High 7.8) | O3 Security