Vulnerability in postgresql (CVE-2026-6472)
Summary
Vulnerability in postgresql (CVE-2026-6472). Risk of unauthorized operations or information disclosure. 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.
Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. 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-6472 has been found in postgresql.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/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-6472" on the vendor's site.
CVE-2026-6472 (postgresql) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
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-862) exists in postgresql.
Check the vendor advisory for the affected versions of postgresql.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
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-6472 postgresql17 Fixed in: 17.10-r0
- BellSoft Alpaquita BELL-CVE-2026-6472 postgresql15 Fixed in: 15.18-r0
- Debian DEBIAN-CVE-2026-6472 postgresql-13
- Ubuntu UBUNTU-CVE-2026-6472 postgresql-9.3
References
- advisory postgresql.org
- web nvd.nist.gov
- web postgresql.org
- web github.com