Is Npgsql 6.0 vulnerable?

NuGet · 14 releases from 6.0.0 to 6.0.13 · latest Npgsql is 10.0.3 · checked 18 Nov 2026

No known advisories in the last release

Npgsql 6.0.13, the last 6.0 release, has no known advisories. 1 advisory affects earlier 6.0.x releases, so update to 6.0.13.

Update within 6.0:dotnet add package Npgsql --version 6.0.13

Is your project on an affected Npgsql?

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 6.0.x, affecting earlier releases

  • HighCVE-2024-32655GHSA-x9vc-6hfv-hg8c9 May 2024

    Npgsql vulnerable to SQL Injection via Protocol Message Size Overflow

    Affected
    >=8.0.0 <8.0.3 · <4.0.14 · >=4.1.0 <4.1.13 · >=5.0.0 <5.0.18 · >=6.0.0 <6.0.11 · >=7.0.0 <7.0.7
    Fixed in
    4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7, 8.0.3

Every Npgsql 6.0.x release

Affected: 6.0.0 to 6.0.10. 6.0.11 and later are not affected. Latest Npgsql: 10.0.3.

VersionKnown advisories
Npgsql 6.0.13None
Npgsql 6.0.12None
Npgsql 6.0.11None
Npgsql 6.0.10CVE-2024-32655
Npgsql 6.0.9CVE-2024-32655
Npgsql 6.0.8CVE-2024-32655
Npgsql 6.0.7CVE-2024-32655
Npgsql 6.0.6CVE-2024-32655
Npgsql 6.0.5CVE-2024-32655
Npgsql 6.0.4CVE-2024-32655
Npgsql 6.0.3CVE-2024-32655
Npgsql 6.0.2CVE-2024-32655
Npgsql 6.0.1CVE-2024-32655
Npgsql 6.0.0CVE-2024-32655

Which of your client projects are still on Npgsql 6.0?

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

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