SQL Injection in postgresql (CVE-2026-6476)
Summary
SQL injection in postgresql (CVE-2026-6476). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 17.10.0, 18.4.0 or later.
Original description
The description as published by the source.
SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.
Source: GitHub Security Advisories (Global) 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-6476 has been found in postgresql.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade postgresql to 17.10.0, 18.4.0 or later.
If unsure, ask your IT team or search "postgresql CVE-2026-6476" on the vendor's site.
CVE-2026-6476 (postgresql) — CWE-89 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 17.10.0, 18.4.0 — apply immediately
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 postgresql.
Check the vendor advisory for the affected versions of postgresql.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 17.10.0, 18.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'postgresql' . 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 'postgresql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
postgresqlを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade postgresql to 17.10.0, 18.4.0ステージング環境で 17.10.0, 18.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- Alpine Linux ALPINE-CVE-2026-6476 postgresql17 Fixed in: 17.10-r0
- BellSoft Alpaquita BELL-CVE-2026-6476 postgresql17 Fixed in: 17.10-r0
- Debian DEBIAN-CVE-2026-6476 postgresql-17 Fixed in: 17.10-0+deb13u1
- Ubuntu UBUNTU-CVE-2026-6476 postgresql-9.3
References
- web nvd.nist.gov
- web postgresql.org
- web github.com
- web postgresql.org