Is github.com/jackc/pgx/v5 5.7 vulnerable?

Go · 7 releases from 5.7.0 to 5.7.6 · 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.7.6, the last 5.7 release, is affected by 6 known security advisories (2 critical, 4 low), including CVE-2026-33816, CVE-2026-33815, CVE-2026-41889. Upgrade to 5.9.2 or later to fix all of them.

Upgrade with:go get github.com/jackc/pgx/v5@v5.9.2

Is your project on an affected github.com/jackc/pgx/v5?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.7.6

  • LowCVE-2026-41889GO-2026-500422 Jun 2026

    SQL Injection via placeholder confusion with dollar quoted string literals in github.com/jackc/pgx

    Affected
    <5.9.2
    Fixed in
    5.9.2
  • LowCVE-2026-41889GHSA-j88v-2chj-qfwx22 Apr 2026

    pgx: SQL Injection via placeholder confusion with dollar quoted string literals

    Affected
    <5.9.2
    Fixed in
    5.9.2
  • CriticalCVE-2026-33816GHSA-9jj7-4m8r-rfcm7 Apr 2026

    Memory-safety vulnerability in github.com/jackc/pgx/v5.

    Affected
    <5.9.0
    Fixed in
    5.9.0
  • CriticalCVE-2026-33815GHSA-xgrm-4fwx-7qm87 Apr 2026

    pgx contains memory-safety vulnerability

    Affected
    <5.9.0
    Fixed in
    5.9.0
  • LowCVE-2026-33815GO-2026-47717 Apr 2026

    CVE-2026-33815 in github.com/jackc/pgx

    Affected
    <5.9.0
    Fixed in
    5.9.0
  • LowCVE-2026-33816GO-2026-47727 Apr 2026

    CVE-2026-33816 in github.com/jackc/pgx

    Affected
    <5.9.0
    Fixed in
    5.9.0

Every github.com/jackc/pgx/v5 5.7.x release

Affected: 5.7.0 to 5.7.6. Latest github.com/jackc/pgx/v5: 5.13.0.

VersionKnown advisories
github.com/jackc/pgx/v5 5.7.6CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.5CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.4CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.3CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.2CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.1CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816
github.com/jackc/pgx/v5 5.7.0CVE-2026-41889, CVE-2026-41889, CVE-2026-33816, CVE-2026-33815, CVE-2026-33815, CVE-2026-33816

Which of your client projects are still on github.com/jackc/pgx/v5 5.7?

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

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.