NuGet.Common vulnerabilities
Common utilities and interfaces for all NuGet libraries.
- Registry
- NuGet
- Latest
- 8.0.0
- License
- Apache-2.0
1 known advisory
The latest version, 8.0.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
dotnet add package NuGet.Common --version 8.0.0Is your project on an affected NuGet.Common?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for NuGet.Common
NuGet Client Remote Code Execution Vulnerability
- Affected
- >=6.0.0 <6.0.5 · >=6.2.0 <6.2.4 · >=6.3.0 <6.3.3 · >=6.4.0 <6.4.2 · >=6.5.0 <6.5.1 · >=6.6.0 <6.6.1 · >=4.6.0 <5.11.5
- Fixed in
- 5.11.5, 6.0.5, 6.2.4, 6.3.3, 6.4.2, 6.5.1, 6.6.1
Is your NuGet.Common version vulnerable?
- NuGet.Common 8.0No known advisories in 8.0.0
- NuGet.Common 7.9No known advisories in 7.9.0
- NuGet.Common 7.6No known advisories in 7.6.0
- NuGet.Common 7.3No known advisories in 7.3.1
- NuGet.Common 7.0No known advisories in 7.0.3
- NuGet.Common 6.14No known advisories in 6.14.3
- NuGet.Common 6.13No known advisories in 6.13.2
- NuGet.Common 6.12No known advisories in 6.12.5
- NuGet.Common 6.11No known advisories in 6.11.2
- NuGet.Common 6.10No known advisories in 6.10.2
- NuGet.Common 6.9No known advisories in 6.9.1
Which of your client projects still run an old NuGet.Common?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.