CVE-2026-6477
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS probability
- 0.45%
- CWE
- CWE-242
- Published
- 2026-05-14
- Last modified
- 2026-08-25
Affected products
- n/a PostgreSQL
- n/a PostgreSQL
- n/a PostgreSQL
- n/a PostgreSQL
- n/a PostgreSQL
Weakness type
Related vulnerabilities
- CVE-2026-11980 — Code execution in IBM Desktop App
- CVE-2025-1994 — IBM Cognos Command Center code execution
- CVE-2025-49215 — A post-auth SQL injection vulnerability in the Trend Micro Endpoint Encryption PolicyServer could...
- CVE-2025-1331 — IBM CICS TX code execution
- CVE-2024-52324 — Ruijie Reyee OS Use of Inherently Dangerous Function
- CVE-2021-40698 — ColdFusion Use of Inherently Dangerous Function Leads To Security feature bypass
- CVE-2022-36310 — Airspan AirVelocity 1500 software prior to version 15.18.00.2511 had NET-SNMP-EXTEND-MIB enabled on...
- CVE-2021-42543 — AzeoTech DAQFactory