← Back
CVE-2026-6474
medium
CVSS 4.3
Vulnerability in postgresql (CVE-2026-6474)
Summary
vulnerability in postgresql (CVE-2026-6474). 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.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-6474** has been found in postgresql.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/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-6474" on the vendor's site.
CVE-2026-6474 (postgresql) — CWE-134 / CVSS v3 4.3
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.
❓ What is the problem
**A vulnerability** (CWE-134) exists in postgresql.
📍 Affected scope
postgresql — .
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply 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 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
postgresql
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"14.23.0"},{"introduced":"15.0.0"},{"fixed":"15.18.0"},{"introduced":"16.0.0"},{"fixed":"16.14.0"},{"introduced":"17.0.0"},{"fixed":"17.10.0"},{"introduced":"18.0.0"},{"fixed":"18.4.0"}]}]