What is CVE-2022-41032?

CVE-2022-41032 is a high-severity improper privilege management vulnerability in NuGet.Commands (nuget), affecting versions >= 4.6.0, < 4.9.6. It is fixed in 4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.

How severe is CVE-2022-41032?

CVE-2022-41032 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-41032?

NuGet.Commands (nuget) versions >= 4.6.0, = 4.6.0, = 4.6.0, < 4.9.6.

Is there a fix for CVE-2022-41032?

Yes. CVE-2022-41032 is fixed in 4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1. Upgrade to this version or later.

Is CVE-2022-41032 exploitable, and should I be worried?

Whether CVE-2022-41032 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-41032 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-41032?

Upgrade: NuGet.Commands to 4.9.6 or later, NuGet.Commands to 5.7.3 or later, NuGet.Commands to 5.9.3 or later, NuGet.Commands to 5.11.3 or later, NuGet.Commands to 6.0.3 or later, NuGet.Commands to 6.2.2 or later, NuGet.Commands to 6.3.1 or later, NuGet.CommandLine to 4.9.6 or later, NuGet.CommandLine to 5.7.3 or later, NuGet.CommandLine to 5.9.3 or later, NuGet.CommandLine to 5.11.3 or later, NuGet.CommandLine to 6.0.3 or later, NuGet.CommandLine to 6.2.2 or later, NuGet.CommandLine to 6.3.1 or later, NuGet.Protocol to 4.9.6 or later, NuGet.Protocol to 5.7.3 or later, NuGet.Protocol to 5.9.3 or later, NuGet.Protocol to 5.11.3 or later, NuGet.Protocol to 6.0.3 or later, NuGet.Protocol to 6.2.2 or later, NuGet.Protocol to 6.3.1 or later.

CVE-2022-41032 in NuGet.Commands

Q: How severe is CVE-2022-41032?

CVE-2022-41032 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-41032?

NuGet.Commands (nuget) versions >= 4.6.0, = 4.6.0, = 4.6.0, < 4.9.6.

Q: Is there a fix for CVE-2022-41032?

Yes. CVE-2022-41032 is fixed in 4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1. Upgrade to this version or later.

Q: Is CVE-2022-41032 exploitable, and should I be worried?

Whether CVE-2022-41032 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-41032 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-41032?

Upgrade: NuGet.Commands to 4.9.6 or later, NuGet.Commands to 5.7.3 or later, NuGet.Commands to 5.9.3 or later, NuGet.Commands to 5.11.3 or later, NuGet.Commands to 6.0.3 or later, NuGet.Commands to 6.2.2 or later, NuGet.Commands to 6.3.1 or later, NuGet.CommandLine to 4.9.6 or later, NuGet.CommandLine to 5.7.3 or later, NuGet.CommandLine to 5.9.3 or later, NuGet.CommandLine to 5.11.3 or later, NuGet.CommandLine to 6.0.3 or later, NuGet.CommandLine to 6.2.2 or later, NuGet.CommandLine to 6.3.1 or later, NuGet.Protocol to 4.9.6 or later, NuGet.Protocol to 5.7.3 or later, NuGet.Protocol to 5.9.3 or later, NuGet.Protocol to 5.11.3 or later, NuGet.Protocol to 6.0.3 or later, NuGet.Protocol to 6.2.2 or later, NuGet.Protocol to 6.3.1 or later.

Summary

NuGet Elevation of Privilege Vulnerability

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.

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

Impact

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2022-41032 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1); upgrading removes the vulnerable code path.

Affected versions

NuGet.Commands (>= 4.6.0, < 4.9.6) NuGet.Commands (>= 5.0.0, < 5.7.3) NuGet.Commands (>= 5.8.0, < 5.9.3) NuGet.Commands (>= 5.10.0, < 5.11.3) NuGet.Commands (>= 6.0.0, < 6.0.3) NuGet.Commands (>= 6.1.0, < 6.2.2) NuGet.Commands (>= 6.3.0, < 6.3.1) NuGet.CommandLine (>= 4.6.0, < 4.9.6) NuGet.CommandLine (>= 5.0.0, < 5.7.3) NuGet.CommandLine (>= 5.8.0, < 5.9.3) NuGet.CommandLine (>= 5.10.0, < 5.11.3) NuGet.CommandLine (>= 6.0.0, < 6.0.3) NuGet.CommandLine (>= 6.1.0, < 6.2.2) NuGet.CommandLine (>= 6.3.0, < 6.3.1) NuGet.Protocol (>= 4.6.0, < 4.9.6) NuGet.Protocol (>= 5.0.0, < 5.7.3) NuGet.Protocol (>= 5.8.0, < 5.9.3) NuGet.Protocol (>= 5.10.0, < 5.11.3) NuGet.Protocol (>= 6.0.0, < 6.0.3) NuGet.Protocol (>= 6.1.0, < 6.2.2) NuGet.Protocol (>= 6.3.0, < 6.3.1)

Security releases

NuGet.Commands → 4.9.6 (nuget) NuGet.Commands → 5.7.3 (nuget) NuGet.Commands → 5.9.3 (nuget) NuGet.Commands → 5.11.3 (nuget) NuGet.Commands → 6.0.3 (nuget) NuGet.Commands → 6.2.2 (nuget) NuGet.Commands → 6.3.1 (nuget) NuGet.CommandLine → 4.9.6 (nuget) NuGet.CommandLine → 5.7.3 (nuget) NuGet.CommandLine → 5.9.3 (nuget) NuGet.CommandLine → 5.11.3 (nuget) NuGet.CommandLine → 6.0.3 (nuget) NuGet.CommandLine → 6.2.2 (nuget) NuGet.CommandLine → 6.3.1 (nuget) NuGet.Protocol → 4.9.6 (nuget) NuGet.Protocol → 5.7.3 (nuget) NuGet.Protocol → 5.9.3 (nuget) NuGet.Protocol → 5.11.3 (nuget) NuGet.Protocol → 6.0.3 (nuget) NuGet.Protocol → 6.2.2 (nuget) NuGet.Protocol → 6.3.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

If you're using NuGet.exe 6.3.0 or lower, you should download and install 6.3.1 from https://dist.nuget.org/win-x86-commandline/v6.3.1/nuget.exe .
If you're using NuGet.exe 6.2.1 or lower, you should download and install 6.2.2 from https://dist.nuget.org/win-x86-commandline/v6.2.2/nuget.exe .
If you're using NuGet.exe 6.0.2 or lower, you should download and install 6.0.3 from https://dist.nuget.org/win-x86-commandline/v6.0.3/nuget.exe .
If you're using NuGet.exe 5.11.2 or lower, you should download and install 5.11.3 from https://dist.nuget.org/win-x86-commandline/v5.11.3/nuget.exe .
If you're using NuGet.exe 5.9.2 or lower, you should download and install 5.9.3 from https://dist.nuget.org/win-x86-commandline/v5.9.3/nuget.exe .
If you're using NuGet.exe 5.7.2 or lower, you should download and install 5.7.3 from https://dist.nuget.org/win-x86-commandline/v5.7.3/nuget.exe .
If you're using NuGet.exe 4.9.5 or lower, you should download and install 4.9.6 from https://dist.nuget.org/win-x86-commandline/v4.9.6/nuget.exe .
If you're using .NET Core 6.0, you should download and install Runtime 6.0.10 or SDK 6.0.110 (for Visual Studio 2022 v17.0) or SDK 6.0.402 (for Visual Studio 2022 v17.3) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
If you're using .NET Core 3.1, you should download and install Runtime 3.1.30 or SDK 3.1.424 (for Visual Studio 2019 v16.9 or Visual Studio 2019 v16.11 or Visual Studio 2022 v17.0 or Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/3.1.

.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.

Frequently Asked Questions

What is CVE-2022-41032? CVE-2022-41032 is a high-severity improper privilege management vulnerability in NuGet.Commands (nuget), affecting versions >= 4.6.0, < 4.9.6. It is fixed in 4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
How severe is CVE-2022-41032? CVE-2022-41032 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-41032?
- NuGet.Commands (nuget) (versions >= 4.6.0, < 4.9.6)
- NuGet.CommandLine (nuget) (versions >= 4.6.0, < 4.9.6)
- NuGet.Protocol (nuget) (versions >= 4.6.0, < 4.9.6)
Is there a fix for CVE-2022-41032? Yes. CVE-2022-41032 is fixed in 4.9.6, 5.7.3, 5.9.3, 5.11.3, 6.0.3, 6.2.2, 6.3.1. Upgrade to this version or later.
Is CVE-2022-41032 exploitable, and should I be worried? Whether CVE-2022-41032 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-41032 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-41032?
- Upgrade NuGet.Commands to 4.9.6 or later
- Upgrade NuGet.Commands to 5.7.3 or later
- Upgrade NuGet.Commands to 5.9.3 or later
- Upgrade NuGet.Commands to 5.11.3 or later
- Upgrade NuGet.Commands to 6.0.3 or later
- Upgrade NuGet.Commands to 6.2.2 or later
- Upgrade NuGet.Commands to 6.3.1 or later
- Upgrade NuGet.CommandLine to 4.9.6 or later
- Upgrade NuGet.CommandLine to 5.7.3 or later
- Upgrade NuGet.CommandLine to 5.9.3 or later
- Upgrade NuGet.CommandLine to 5.11.3 or later
- Upgrade NuGet.CommandLine to 6.0.3 or later
- Upgrade NuGet.CommandLine to 6.2.2 or later
- Upgrade NuGet.CommandLine to 6.3.1 or later
- Upgrade NuGet.Protocol to 4.9.6 or later
- Upgrade NuGet.Protocol to 5.7.3 or later
- Upgrade NuGet.Protocol to 5.9.3 or later
- Upgrade NuGet.Protocol to 5.11.3 or later
- Upgrade NuGet.Protocol to 6.0.3 or later
- Upgrade NuGet.Protocol to 6.2.2 or later
- Upgrade NuGet.Protocol to 6.3.1 or later

Other vulnerabilities in NuGet.Commands

CVE-IDSeverityPackage summary

CVE-2023-29337HighMicrosoft.Build.NuGetSdkResolver: NuGet Client Remote Code Execution Vulnerability CVE-2022-30184MediumNuGet.Commands: Potential leak of NuGet.org API key CVE-2019-0976MediumNuGet.Commands: NuGet Package Manager Tampering Vulnerability