← Back
CVE-2026-41889
critical
CVSS 9.8
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SQL injection** (CWE-89) exists in github.com/jackc/pgx/v5.
📍 Affected scope
github.com/jackc/pgx/v5 — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.9.2**.
🛡️ Workaround
Workaround: Do not use the simple protocol to execute queries matching all the above conditions.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/jackc/pgx/v5 to 5.9.2ステージング環境で 5.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/jackc/pgx/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.9.2"}]}]
go
github.com/jackc/pgx/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"4.18.3"}]}]
go
github.com/jackc/pgx
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"3.6.2"}]}]