SQL injection in github.com/jackc/pgproto3 and github.com/jackc/pgx
Published 14 Mar 2024 · Updated 4 Feb 2026
Is your project on an affected github.com/jackc/pgproto3/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <2.3.3
- Fixed in
- 2.3.3
go get github.com/jackc/pgproto3/v2@v2.3.3- Affected
- All versions
- Fixed in
- No fix released
- Affected
- <4.18.2
- Fixed in
- 4.18.2
go get github.com/jackc/pgx/v4@v4.18.2- Affected
- >=5.0.0 <5.5.4
- Fixed in
- 5.5.4
go get github.com/jackc/pgx/v5@v5.5.4Details
An integer overflow in the calculated message size of a query or bind message could allow a single large message to be sent as multiple messages under the attacker's control. This could lead to SQL injection if an attacker can cause a single query or bind message to exceed 4 GB in size.
Is GO-2024-2606 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/jackc/pgproto3/v2, and gives you the command that fixes it.
More advisories for github.com/jackc/pgproto3/v2
- HighCVE-2026-32286Denial of service in github.com/jackc/pgproto3/v2 · 18 Mar 2026
- LowCVE-2026-32286Denial of service in github.com/jackc/pgproto3/v2 · 16 Mar 2026
References
- Advisorygithub.com/jackc/pgx/security/advisories/GHSA-mrww-27vc-gghv
- Fixgithub.com/jackc/pgproto3/commit/945c2126f6db8f3bea7eeebe307c01fe92bca007
- Fixgithub.com/jackc/pgx/commit/adbb38f298c76e283ffc7c7a3f571036fea47fd4
- Fixgithub.com/jackc/pgx/commit/c543134753a0c5d22881c12404025724cb05ffd8
- Fixgithub.com/jackc/pgx/commit/f94eb0e2f96782042c96801b5ac448f44f0a81df
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.