NuGet.Packaging vulnerabilities

NuGet's understanding of packages. Reading nuspec, nupkgs and package signing.

Registry
NuGet
Latest
8.0.0
License
Apache-2.0

2 known advisories

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.Packaging --version 8.0.0

Is your project on an affected NuGet.Packaging?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for NuGet.Packaging

  • LowGHSA-g4vj-cjjj-v7hg14 Apr 2026

    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
  • CriticalCVE-2024-0057GHSA-68w7-72jg-6qpp13 Feb 2024

    NuGet Client Security Feature Bypass Vulnerability

    Affected
    >=4.6.0 <5.11.6 · >=6.0.0 <6.0.6 · >=6.3.0 <6.3.4 · >=6.4.0 <6.4.3 · >=6.6.0 <6.6.2 · >=6.7.0 <6.7.1 · >=6.8.0 <6.8.1
    Fixed in
    5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1

Is your NuGet.Packaging version vulnerable?

Which of your client projects still run an old NuGet.Packaging?

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.