Is Npgsql 3.1 vulnerable?
NuGet · 11 releases from 3.1.0 to 3.1.10 · latest Npgsql is 10.0.3 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. Npgsql 3.1.10, the last 3.1 release, is affected by 1 known security advisory (1 high), including CVE-2024-32655. Upgrade to 4.0.14 or later to fix all of them.
dotnet add package Npgsql --version 4.0.14Is your project on an affected Npgsql?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting Npgsql 3.1.10
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 3.1.x release
Affected: 3.1.0 to 3.1.10. Latest Npgsql: 10.0.3.
| Version | Known advisories |
|---|---|
| Npgsql 3.1.10 | CVE-2024-32655 |
| Npgsql 3.1.9 | CVE-2024-32655 |
| Npgsql 3.1.8 | CVE-2024-32655 |
| Npgsql 3.1.7 | CVE-2024-32655 |
| Npgsql 3.1.6 | CVE-2024-32655 |
| Npgsql 3.1.5 | CVE-2024-32655 |
| Npgsql 3.1.4 | CVE-2024-32655 |
| Npgsql 3.1.3 | CVE-2024-32655 |
| Npgsql 3.1.2 | CVE-2024-32655 |
| Npgsql 3.1.1 | CVE-2024-32655 |
| Npgsql 3.1.0 | CVE-2024-32655 |
Which of your client projects are still on Npgsql 3.1?
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.