Vulnerability in postgresql (CVE-2026-6475)
Summary
Vulnerability in postgresql (CVE-2026-6475). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0 or later.
Original description
The description as published by the source.
Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
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-6475 has been found in postgresql.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade postgresql to 14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0 or later.
If unsure, ask your IT team or search "postgresql CVE-2026-6475" on the vendor's site.
CVE-2026-6475 (postgresql) — CWE-61 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 14.23.0, 15.18.0, 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.
A vulnerability (CWE-61) exists in postgresql.
Check the vendor advisory for the affected versions of postgresql.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 14.23.0, 15.18.0, 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 14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0ステージング環境で 14.23.0, 15.18.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-6475 postgresql17 Fixed in: 17.10-r0
- BellSoft Alpaquita BELL-CVE-2026-6475 postgresql15 Fixed in: 15.18-r0
- Debian DEBIAN-CVE-2026-6475 postgresql-13
- Ubuntu UBUNTU-CVE-2026-6475 postgresql-9.3
References
- advisory postgresql.org
- web nvd.nist.gov
- web postgresql.org
- web github.com