CVE-2026-41889: pgx: SQL Injection via placeholder confusion with dollar quoted string literals
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: jackc pgx 5.9.2; azl3 keda 2.14.1-14 on Azure Linux 3.0 2.14.1-15; azl3 keda 2.14.1-15 on Azure Linux 3.0 2.14.1-15.
Low priority for now. Upgrade to jackc pgx 5.9.2; azl3 keda 2.14.1-14 on Azure Linux 3.0 2.14.1-15; azl3 keda 2.14.1-15 on Azure Linux 3.0 2.14.1-15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 8, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-89
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 2.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jackc | pgx | cpe:2.3:a:jackc:pgx |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jackc pgxbefore 5.9.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
jackc pgx
- < 5.9.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | golang-github-jackc-pgx-v5 | from 0 | — |
| Go | github.com/jackc/pgx | from 0 | — |
| Go | github.com/jackc/pgx | up to and including 3.6.2 | — |
| Go | github.com/jackc/pgx/v4 | from 0 | — |
| Go | github.com/jackc/pgx/v4 | up to and including 4.18.3 | — |
| Go | github.com/jackc/pgx/v5 | before 5.9.2 | 5.9.2 |
| openSUSE:Leap 16.0 | alloy | before 1.17.0-160000.1.1 | 1.17.0-160000.1.1 |
| openSUSE:Tumbleweed | alloy | before 1.16.1-2.1 | 1.16.1-2.1 |
| openSUSE:Tumbleweed | steampipe | before 2.4.4-1.1 | 2.4.4-1.1 |
| Red Hat:hummingbird:1 | caddy | before 0:2.11.3-0.1.hum1 | 0:2.11.3-0.1.hum1 |
| Red Hat:hummingbird:1 | cosign | before 0:3.1.1-0.1.hum1 | 0:3.1.1-0.1.hum1 |
| Red Hat:hummingbird:1 | go-fdo-server | before 0:1.0.1-0.2.hum1 | 0:1.0.1-0.2.hum1 |
| Red Hat:hummingbird:1 | go-fdo-server-manufacturer | before 0:1.0.1-0.2.hum1 | 0:1.0.1-0.2.hum1 |
| Red Hat:hummingbird:1 | go-fdo-server-owner | before 0:1.0.1-0.2.hum1 | 0:1.0.1-0.2.hum1 |
| Red Hat:hummingbird:1 | go-fdo-server-rendezvous | before 0:1.0.1-0.2.hum1 | 0:1.0.1-0.2.hum1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | alloy | before 1.17.1-150700.15.23.1 | 1.17.1-150700.15.23.1 |
| SUSE:Linux Enterprise Server 16.0 | alloy | before 1.17.0-160000.1.1 | 1.17.0-160000.1.1 |
Same product
jackc: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-33816CVE-2026-33816 in github.com/jackc/pgx39Monitor
- CVE-2026-33815CVE-2026-33815 in github.com/jackc/pgx39Monitor
- CVE-2024-27289pgx SQL Injection via Line Comment Creation32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| jackc pgx | 5.9.2 · description | Vendor (CNA) |
| azl3 keda 2.14.1-14 on Azure Linux 3.0 | 2.14.1-15 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 keda 2.14.1-15 on Azure Linux 3.0 | 2.14.1-15 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 telegraf 1.31.0-22 on Azure Linux 3.0 | 1.31.0-22 · CBL-Mariner Releases | Microsoft (MSRC) |
| Go:github.com/jackc/pgx/v5 | 5.9.2 | Package registry (OSV) |
| opensuse:alloy | 1.16.1-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:steampipe | 2.4.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:caddy | 0:2.11.3-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:cosign | 0:3.1.1-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:go-fdo-server | 0:1.0.1-0.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:go-fdo-server-manufacturer | 0:1.0.1-0.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:go-fdo-server-owner | 0:1.0.1-0.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:go-fdo-server-rendezvous | 0:1.0.1-0.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:alloy | 1.17.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.