CVE-2026-6477 | PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory

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.

Published: 2026-05-14 Last update: 2026-05-18 Assigner: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Conclusion & alert: CVE-2026-6477 is rated Low Risk (39.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.04%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-6477

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-15 0.04%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-6477

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Weakness enumeration for CVE-2026-6477

GitHub Security Advisory for CVE-2026-6477

GHSA-jm5f-gpfq-q9h3 · Severity: high — Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq...

OS Trackers for CVE-2026-6477

vendor priority summary link
debian not yet assigned CVE-2026-6477 not yet assigned priority: Debian including 4 source packages (postgresql-13, postgresql-15, postgresql-17, postgresql-18), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-6477
suse high CVE-2026-6477 severity important: SUSE including 176 source package names (libecpg6-17.10-3.27.1, libecpg6-18.4-150200.5.12.1, …), 773 product×package rows across 31 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (31 product lines)): First Fixed 340, Fixed 269, Known Not Affected 164. https://www.suse.com/security/cve/CVE-2026-6477/
ubuntu medium CVE-2026-6477 medium priority: Ubuntu including 8 source packages (postgresql-10, postgresql-12, …), 44 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 28, needs-triage 7, ignored 4, released 4, deferred 1. https://ubuntu.com/security/CVE-2026-6477

Affected software / configurations for CVE-2026-6477

Vendor Product Version Raw CPE
postgresql postgresql < 14.23 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 15.0, < 15.18 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 16.0, < 16.14 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 17.0, < 17.10 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 18.0, < 18.4 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*

References for CVE-2026-6477

cvelogic Threat Intelligence