Is NuGet.Packaging 7.0 vulnerable?

NuGet · 3 releases from 7.0.0 to 7.0.3 · latest NuGet.Packaging is 8.0.0 · checked 18 Nov 2026

No known advisories in the last release

NuGet.Packaging 7.0.3, the last 7.0 release, has no known advisories. 1 advisory affects earlier 7.0.x releases, so update to 7.0.3.

Update within 7.0:dotnet add package NuGet.Packaging --version 7.0.3

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

Fixed within 7.0.x, affecting earlier releases

  • 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

Every NuGet.Packaging 7.0.x release

Affected: 7.0.0 to 7.0.1. 7.0.3 is not affected. Latest NuGet.Packaging: 8.0.0.

VersionKnown advisories
NuGet.Packaging 7.0.3None
NuGet.Packaging 7.0.1GHSA-g4vj-cjjj-v7hg
NuGet.Packaging 7.0.0GHSA-g4vj-cjjj-v7hg

Which of your client projects are still on NuGet.Packaging 7.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact NuGet.Packaging version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other NuGet.Packaging 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.