PostgreSQL

Recent PostgreSQL Security Advisories

By the Year

In 2026 there have been 45 vulnerabilities in PostgreSQL with an average score of 7.1 out of ten. Last year, in 2025 PostgreSQL had 9 security vulnerabilities published. That is, 36 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 2.10.

Recent PostgreSQL Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2026-14671	Aug 13, 2026	PostgreSQL refint Type Confusion Exec as OS User pre-18.5 Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-6471	Aug 13, 2026	PostgreSQL auth bypass via logical decoding plugin DLopen in 18.x/17.x Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-6469	Aug 13, 2026	PostgreSQL <18.5: ALTER TYPE Ownership Bug Enables Priv Escalation Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves nothing in many ownership arrangements. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-6470	Aug 13, 2026	PostgreSQL DDL Auth Bypass Enables DoS on ALTER/ DROP Type (pre-18.5) Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-6464	Aug 13, 2026	PostgreSQL Before 18.5: Untrusted Data Inclusion via psql COPY Error Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-18408	Aug 13, 2026	Untrusted Data Inclusion in pg_dump (PostgreSQL <18.5) Enables Code Exec via psql \restrict Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-19385	Aug 13, 2026	Heap Buffer Overflow in PostgreSQL pg_dump (v<18.5) Enables OS-Level RCE Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-18024	Aug 13, 2026	PostgreSQL ascii() buffer over-read before 18.5/17.11/16.15/15.19/14.24 Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end of a specific allocation, via a crafted text value. This is the same class of defect that CVE-2026-2006 fixed, though this instance has less impact. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-16241	Aug 13, 2026	PostgreSQL ECPG Int Uflow 18.5 allows temp DoS via bytea Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix. The client overwrites a huge memory region with bytes outside attacker knowledge or control. This typically yields a simple SIGSEGV, but rare cases might achieve client-specific integrity impact via the write. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL
CVE-2026-16239	Aug 13, 2026	PostgreSQL <18.5 Type Confusion Enables OS Exec via Cursor Re-Creation Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.	PostgreSQL