SQL Injection in postgresql (CVE-2026-6638)
Summary
SQL injection in postgresql (CVE-2026-6638). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 16.14.0, 17.10.0, 18.4.0 or later.
Original description
The description as published by the source.
SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table creator to execute arbitrary SQL with the subscription's publication-side credentials. The attack takes effect at the next REFRESH PUBLICATION. Within major versions 16, 17, and 18, minor versions before PostgreSQL 18.4, 17.10, and 16.14 are affected. Versions before PostgreSQL 16 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-6638 has been found in postgresql.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade postgresql to 16.14.0, 17.10.0, 18.4.0 or later.
If unsure, ask your IT team or search "postgresql CVE-2026-6638" on the vendor's site.
CVE-2026-6638 (postgresql) — CWE-89 / CVSS v3 3.7
Attack vector: remote (network-reachable)
Patched: 16.14.0, 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: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 16.14.0, 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 16.14.0, 17.10.0, 18.4.0ステージング環境で 16.14.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-6638 postgresql17 Fixed in: 17.10-r0
- BellSoft Alpaquita BELL-CVE-2026-6638 postgresql17 Fixed in: 17.10-r0
- Debian DEBIAN-CVE-2026-6638 postgresql-17 Fixed in: 17.10-0+deb13u1
- Ubuntu UBUNTU-CVE-2026-6638 postgresql-9.3
References
- advisory postgresql.org
- web nvd.nist.gov
- web postgresql.org
- web github.com