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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-6477US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:21182WEB
- https://access.redhat.com/errata/RHSA-2026:22878WEB
- https://access.redhat.com/errata/RHSA-2026:26181WEB
- https://access.redhat.com/errata/RHSA-2026:26203WEB
- https://access.redhat.com/errata/RHSA-2026:26204WEB
- https://access.redhat.com/errata/RHSA-2026:26524WEB
- https://access.redhat.com/errata/RHSA-2026:26525WEB
- https://access.redhat.com/errata/RHSA-2026:26561WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan