Is github.com/jackc/pgx/v5 5.5 vulnerable?
Go · 6 releases from 5.5.0 to 5.5.5 · latest github.com/jackc/pgx/v5 is 5.13.0 · checked 18 Nov 2026
Yes: 6 known advisories
Yes. github.com/jackc/pgx/v5 5.5.5, the last 5.5 release, is affected by 6 known security advisories (2 critical, 4 low), including CVE-2026-33816, CVE-2026-33815, CVE-2026-41889. 4 more affect earlier 5.5.x releases. Upgrade to 5.9.2 or later to fix all of them.
go get github.com/jackc/pgx/v5@v5.9.2Is your project on an affected github.com/jackc/pgx/v5?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/jackc/pgx/v5 5.5.5
SQL Injection via placeholder confusion with dollar quoted string literals in github.com/jackc/pgx
- Affected
- <5.9.2
- Fixed in
- 5.9.2
pgx: SQL Injection via placeholder confusion with dollar quoted string literals
- Affected
- <5.9.2
- Fixed in
- 5.9.2
Memory-safety vulnerability in github.com/jackc/pgx/v5.
- Affected
- <5.9.0
- Fixed in
- 5.9.0
pgx contains memory-safety vulnerability
- Affected
- <5.9.0
- Fixed in
- 5.9.0
CVE-2026-33815 in github.com/jackc/pgx
- Affected
- <5.9.0
- Fixed in
- 5.9.0
CVE-2026-33816 in github.com/jackc/pgx
- Affected
- <5.9.0
- Fixed in
- 5.9.0
Fixed within 5.5.x, affecting earlier releases
Panic in Pipeline when PgConn is busy or closed in github.com/jackc/pgx
- Affected
- <5.5.2
- Fixed in
- 5.5.2
Panic in Pipeline when PgConn is busy or closed in github.com/jackc/pgx
- Affected
- >=5.0.0-alpha.5 <5.5.2
- Fixed in
- 5.5.2
SQL injection in github.com/jackc/pgproto3 and github.com/jackc/pgx
- Affected
- >=5.0.0 <5.5.4
- Fixed in
- 5.5.4
pgx SQL Injection via Protocol Message Size Overflow
- Affected
- >=5.0.0 <5.5.4
- Fixed in
- 5.5.4
Every github.com/jackc/pgx/v5 5.5.x release
Affected: 5.5.0 to 5.5.5. Latest github.com/jackc/pgx/v5: 5.13.0.
| Version | Known advisories |
|---|---|
| github.com/jackc/pgx/v5 5.5.5 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816 |
| github.com/jackc/pgx/v5 5.5.4 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816 |
| github.com/jackc/pgx/v5 5.5.3 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816, CVE-2024-27304, CVE-2024-27304 |
| github.com/jackc/pgx/v5 5.5.2 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816, CVE-2024-27304, CVE-2024-27304 |
| github.com/jackc/pgx/v5 5.5.1 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816, GHSA-fqpg-rq76-99pq, GO-2024-2567, CVE-2024-27304, CVE-2024-27304 |
| github.com/jackc/pgx/v5 5.5.0 | CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816, GHSA-fqpg-rq76-99pq, GO-2024-2567, CVE-2024-27304, CVE-2024-27304 |
Which of your client projects are still on github.com/jackc/pgx/v5 5.5?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/jackc/pgx/v5 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/jackc/pgx/v5 versions
- github.com/jackc/pgx/v5 5.8
- github.com/jackc/pgx/v5 5.7
- github.com/jackc/pgx/v5 5.6
- github.com/jackc/pgx/v5 5.4
- github.com/jackc/pgx/v5 5.3
- github.com/jackc/pgx/v5 5.2
- github.com/jackc/pgx/v5 5.13
- github.com/jackc/pgx/v5 5.12
- github.com/jackc/pgx/v5 5.11
- github.com/jackc/pgx/v5 5.10
- github.com/jackc/pgx/v5 5.9
- All github.com/jackc/pgx/v5 advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.