SQL Injection in github.com/jackc/pgx/v5 (CVE-2026-41889)
Summary
SQL injection in github.com/jackc/pgx/v5 (CVE-2026-41889). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.9.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41889 has been found in github.com/jackc/pgx/v5.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/jackc/pgx/v5 to 5.9.2 or later.
If unsure, ask your IT team or search "github.com/jackc/pgx/v5 CVE-2026-41889" on the vendor's site.
CVE-2026-41889 (github.com/jackc/pgx/v5) — CWE-89 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.9.2 — apply immediately
Workaround: Do not use the simple protocol to execute queries matching all the above conditions.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in github.com/jackc/pgx/v5.
Check the vendor advisory for the affected versions of github.com/jackc/pgx/v5.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 5.9.2.
Workaround: Do not use the simple protocol to execute queries matching all the above conditions.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/jackc/pgx/v5' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/jackc/pgx/v5' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/jackc/pgx/v5を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Do not use the simple protocol to execute queries matching all the above conditions.パッチが適用されるまでの応急処置として、Do not use the simple protocol to execute queries matching all the above conditions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/jackc/pgx/v5 to 5.9.2ステージング環境で 5.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41889 golang-github-jackc-pgx-v5
- Ubuntu UBUNTU-CVE-2026-41889 golang-github-jackc-pgx-v5
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com