Is NuGet.CommandLine 6.11 vulnerable?
NuGet · 3 releases from 6.11.0 to 6.11.2 · latest NuGet.CommandLine is 8.0.0 · checked 18 Nov 2026
No known advisories in the last release
NuGet.CommandLine 6.11.2, the last 6.11 release, has no known advisories. 1 advisory affects earlier 6.11.x releases, so update to 6.11.2.
dotnet add package NuGet.CommandLine --version 6.11.2Is your project on an affected NuGet.CommandLine?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 6.11.x, affecting earlier releases
Defense in Depth update for NuGet Client
- Affected
- >=4.9.0 <4.9.7 · >=5.11.0 <5.11.7 · >=6.8.0 <6.8.2 · >=6.11.0 <6.11.2 · >=6.12.0 <6.12.5 · >=6.14.0 <6.14.3 · >=7.0.0 <7.0.3 · >=7.3.0 <7.3.1
- Fixed in
- 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1
Every NuGet.CommandLine 6.11.x release
Affected: 6.11.0 to 6.11.1. 6.11.2 is not affected. Latest NuGet.CommandLine: 8.0.0.
| Version | Known advisories |
|---|---|
| NuGet.CommandLine 6.11.2 | None |
| NuGet.CommandLine 6.11.1 | GHSA-g4vj-cjjj-v7hg |
| NuGet.CommandLine 6.11.0 | GHSA-g4vj-cjjj-v7hg |
Which of your client projects are still on NuGet.CommandLine 6.11?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact NuGet.CommandLine version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other NuGet.CommandLine versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.