Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-6477 high CVSS 8.8

Vulnerability in postgresql (CVE-2026-6477)

Summary

Vulnerability in postgresql (CVE-2026-6477). 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.

Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory. 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-6477 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-6477" on the vendor's site.

CVE-2026-6477 (postgresql) — CWE-242 / 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.

❓ What is the problem

A vulnerability (CWE-242) exists in postgresql.

📍 Affected scope

Check the vendor advisory for the affected versions of postgresql.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'postgresql' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で postgresql を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details