Vulnerability in postgresql (CVE-2026-6575)
Summary
Vulnerability in postgresql (CVE-2026-6575). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 18.4.0 or later.
Original description
The description as published by the source.
Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Within major version 18, minor versions before PostgreSQL 18.4 are affected. Versions before PostgreSQL 18 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-6575 has been found in postgresql.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade postgresql to 18.4.0 or later.
If unsure, ask your IT team or search "postgresql CVE-2026-6575" on the vendor's site.
CVE-2026-6575 (postgresql) — CWE-126 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 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-126) exists in postgresql.
Check the vendor advisory for the affected versions of postgresql.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 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 18.4.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-6575 postgresql18 Fixed in: 18.4-r0
- BellSoft Alpaquita BELL-CVE-2026-6575 postgresql18 Fixed in: 18.4-r0
- Debian DEBIAN-CVE-2026-6575 postgresql-18 Fixed in: 18.4-1
- Ubuntu UBUNTU-CVE-2026-6575 postgresql-9.3
References
- web nvd.nist.gov
- web postgresql.org
- web github.com
- web postgresql.org