dbcve.org
PgxApplication · Jackc

CVE-2026-33816

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 5.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical memory-safety vulnerability in github.com/jackc/pgx/v5, a popular PostgreSQL driver for Go, could allow remote attackers to cause memory corruption or potentially achieve arbitrary code execution via malformed database responses.

MitigationImmediately update pgx/v5 to the latest patched version once available. Review application code using this library and monitor for unusual database interaction patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PgxApplication
Affected:< 5.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if pgx/v5 is used in your project
    Inspect your go.mod file for a line containing 'github.com/jackc/pgx/v5' and note the version number after the space
    Affected if The line exists and shows a version less than 5.9.0 (e.g., require github.com/jackc/pgx/v5 v5.8.0)
  2. Check installed pgx/v5 version via Go
    Run 'go list -m github.com/jackc/pgx/v5' in your project directory
    Affected if The output shows a version lower than 5.9.0 (e.g., v5.8.0, v5.8.1, v5.8.2, etc.)
  3. Verify pgx/v5 is actively imported and used
    Search your codebase for imports of 'github.com/jackc/pgx/v5' using grep or your IDE (e.g., grep -r 'jackc/pgx/v5' *.go)
    Affected if The library is imported in any Go source file in your project
  4. Confirm the application connects to PostgreSQL
    Review your codebase for database connection setup using pgx (look for pgxpool, conn, or driver instances)
    Affected if Your application establishes PostgreSQL connections using pgx driver functionality

You are affected if your project uses github.com/jackc/pgx/v5 at any version below 5.9.0 and actively connects to PostgreSQL using the pgx driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.9.0 or later
Fixed in 5.9.0
Interim mitigation

Immediately update pgx/v5 to the latest patched version once available. Review application code using this library and monitor for unusual database interaction patterns.

Recommended fix High confidence

github.com/jackc/pgx/v5 v5.9.0 or later

  1. Update the go.mod file to require github.com/jackc/pgx/v5 version 5.9.0 or later (e.g., replace the existing pgx requirement with github.com/jackc/pgx/v5 v5.9.0)
  2. Run 'go mod tidy' to update dependencies
  3. Run 'go build ./...' to verify the upgrade compiles successfully
  4. Run existing test suite to verify functionality remains intact
Caveat Minor v5.x within same major version - minimal breaking changes expected, but test thoroughly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33816 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data