How severe is CVE-2026-41889?

No CVSS score has been assigned to CVE-2026-41889 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-41889?

CVE-2026-41889 affects the following packages: github.com/jackc/pgx/v5 (Go), github.com/jackc/pgx/v4 (Go), github.com/jackc/pgx (Go). Ecosystems affected: Go.

How do I fix CVE-2026-41889?

Update github.com/jackc/pgx/v5 to 5.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41889 is resolved across your whole dependency graph.

How do I detect CVE-2026-41889 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jackc/pgx/v5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-41889 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2026-41889 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41889 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-41889?

CVE-2026-41889 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-41889?

CVE-2026-41889 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-41889 published, and has it been updated?

CVE-2026-41889 was published on May 8, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-41889 — pgx

Fix: jackc/pgx@60644f8

CVE-2026-41889 is a SQL Injection vulnerability in github.com/jackc/pgx/v5. A fix is available for github.com/jackc/pgx/v5 — see the affected versions and patch details below.

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

Also known asGHSA-j88v-2chj-qfwxGO-2026-5004

Published

May 8, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41889.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐹github.com/jackc/pgx/v5🐹github.com/jackc/pgx/v4🐹github.com/jackc/pgx

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.
The value of that placeholder is controllable by the attacker.

e.g.

attackValue := `$tag$; drop table canary; --`
_, err = tx.Exec(ctx, `select $tag$ $1 $tag$, $1`, pgx.QueryExecModeSimpleProtocol, attackValue)

This is unlikely to occur outside of a contrived scenario.

Patches

The problem is resolved in v5.9.2.

Workarounds

Do not use the simple protocol to execute queries matching all the above conditions.

Affected Packages

3 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/jackc/pgx/v5`	all versions	5.9.2`go get github.com/jackc/pgx/v5@v5.9.2`
🐹Go	`github.com/jackc/pgx/v4`	all versions	No fix
🐹Go	`github.com/jackc/pgx`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

pgxjackc

< 5.9.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jackc/pgx/v5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jackc/pgx/v5 to 5.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41889 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat has rated this flaw as Moderate because the SQL injection vulnerability in pgx can only be triggered when the non-default simple protocol is used in conjunction with specific query constructions involving PostgreSQL dollar-quoted string literals. Successful exploitation requires multiple uncommon…

Workaround published by Red Hat

Avoid using the non-default simple protocol in applications that use the pgx PostgreSQL driver for Go. The vulnerability is contingent on this non-default protocol and specific SQL query constructs. Configuring applications to use the default extended protocol prevents this issue. If the simple protocol is necessary, ensure that dollar-quoted string literals do not contain attacker-controlled placeholder values.

Source: Red Hat security advisory for CVE-2026-41889 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Advanced Cluster Security 4.9	`advanced-cluster-security/rhacs-main-rhel8:1785413210`	RHSA-2026:48872
Red Hat Advanced Cluster Security for Kubernetes for IBM Power, little endian 4.10	`advanced-cluster-security/rhacs-main-rhel8:1785420959`	RHSA-2026:48913
Red Hat Hardened Images	`go-fdo-server-main-1.0.1-0.2.hum1`	RHSA-2026:15856
Red Hat Hardened Images	`caddy-main-2.11.3-0.1.hum1`	RHSA-2026:16133
Red Hat Hardened Images	`cosign-main-3.1.1-0.1.hum1`	RHSA-2026:25138

Frequently Asked Questions

### Impact SQL Injection can occur when: 1. The non-default simple protocol is used. 2. A dollar quoted string literal is used in the SQL query. 3. That string literal contains text that would be would be interpreted as a placeholder outside of a string literal. 4. The value of that placeholder is controllable by the attacker. e.g. ```go attackValue := `$tag$; drop table canary; --` _, err = tx.Exec(ctx, `select $tag$ $1 $tag$, $1`, pgx.QueryExecModeSimpleProtocol, attackValue) ``` This is unlikely to occur outside of a contrived scenario. ### Patches The problem is resolved in v5.9.2.