dbcve.org
PgxApplication · Jackc

CVE-2026-41889

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

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
pgx is a PostgreSQL driver and toolkit for Go. Prior to version 5.9.2, SQL injection can occur when the non-default simple protocol is used, a dollar quoted string literal is used in the SQL query, that string literal contains text that would be would be interpreted as a placeholder outside of a string literal, and the value of that placeholder is controllable by the attacker. This issue has been patched in version 5.9.2.

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

SQL injection vulnerability in pgx PostgreSQL driver for Go (versions prior to 5.9.2). When using the non-default simple protocol with dollar-quoted string literals that contain text interpretable as placeholders, and an attacker can control the placeholder value, SQL injection becomes possible.

MitigationUpgrade pgx to version 5.9.2 or later. As a workaround, avoid using the simple protocol or ensure dollar-quoted strings do not contain controllable placeholder-like text.

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

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 installed pgx version
    Run 'go list -m all | grep pgx' or check go.mod for the pgx module version
    Affected if The version listed is less than 5.9.2
  2. Check if simple protocol is enabled
    Search your codebase for 'SimpleProtocol' set to true, or 'protocol' config value set to 'simple' in the pgx connection config
    Affected if SimpleProtocol is explicitly set to true in your pgx connection configuration
  3. Verify dollar-quoted strings are in use
    Search your codebase for dollar-quoted string syntax like '$$...$$' or $tag$...$tag$ used in SQL queries
    Affected if Your application code uses dollar-quoted string literals in SQL statements
  4. Determine if user input flows into placeholder positions
    Review code paths where user-controllable data (request parameters, user inputs, external API data) are bound to query parameters when simple protocol is active
    Affected if Untrusted input can be passed as query parameters when using simple protocol with dollar-quoted strings

You are affected if you are using pgx version below 5.9.2 AND have simple protocol enabled AND use dollar-quoted strings with placeholder-like content that accepts user-controlled input.

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.2 or later
Fixed in 5.9.2
Vendor patch github.com →
Interim mitigation

Upgrade pgx to version 5.9.2 or later. As a workaround, avoid using the simple protocol or ensure dollar-quoted strings do not contain controllable placeholder-like text.

Recommended fix High confidence

v5.9.2

  1. Update the pgx version in go.mod to v5.9.2 or later (e.g., replace the import with github.com/jackc/pgx/[email protected])
  2. Run 'go mod tidy' to update dependencies and verify the upgrade succeeds
  3. Rebuild and test the application to confirm the fix is applied
  4. Ensure simple protocol usage is reviewed - consider using the default extended protocol if possible as a defense-in-depth measure

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-41889 — 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-41889 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