PostgreSQL Updates Address 52 Security Flaws Including CVE-2026-6460

The PostgreSQL Global Development Group has released security updates fixing 52 flaws in PostgreSQL, including CVE-2026-6460, a type-confusion vulnerability with a CVSS score of 8.8. The issue can allow a database user who can create or modify objects to execute code on the database server.
Affected versions are all releases before PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25. Code executed through the flaw would inherit the operating-system permissions of the user running PostgreSQL. PostgreSQL 14.25 is the final release for the now end-of-life PostgreSQL 14 branch, while older affected major versions received no update.
A long-standing composite-type flaw
CVE-2026-6460 concerns composite types, whose named fields have individual data types. A field type can be changed while older values remain in other parts of the server. PostgreSQL could then interpret an older value as though it used the replacement type.
The project’s fix adds version checks intended to identify values that no longer match their type. Researcher Mehmet Ince demonstrated a working exploit on PostgreSQL 18.6: it prepares a query holding a value, changes a field type, and then executes the query. His technical write-up shows a crash and a memory-address leak, while omitting the final command-execution SQL.
Ince said he could trigger the crash using a lowest-privileged login role. PostgreSQL’s advisory describes the attacker as someone able to create objects, and Red Hat specifies a database login with permission to create or modify objects. The available advisories do not establish whether a default-privilege account can progress from a crash to code execution.
Managed services and related fixes
The researcher traced the root cause to PostgreSQL’s May 2004 support for changing a column type, while his code-execution technique depends on a change made in May 2015. He also adapted the exploit for managed services and privately shared proofs of concept in August with teams at AWS, Microsoft, Google, Supabase, Databricks and Ubicloud. The write-up does not state the current patch status for each service.
PostgreSQL reported no attacks using CVE-2026-6460, and CISA’s CVE assessment lists exploitation as none. The project assigned an 8.8 score to 32 of the 52 flaws fixed in this release. Its vulnerability index identifies CVE-2026-116322 as the only server flaw that needs neither a login nor user action; it allows an unauthenticated client to restart PostgreSQL 18 servers.
Several fixes also affect client-side utilities. A crafted archive can cause pg_restore to run code as its invoking user, while a compromised source server can cause psql to execute code through the restore script in pg_dump tar output.
Patch, rebuild and review backup operations
Administrators should upgrade to the current minor release for their supported major version, then rebuild or update every C-language extension. Extensions built against older releases may still load but may not receive the protections in these fixes, and some require source changes. Extensions rebuilt for these releases can also fail to load on older servers.
Teams should restart PostgreSQL immediately after updating when it runs outside the package service unit, such as under Patroni. They should update pg_dump, pg_restore, reindexdb and vacuumdb on every machine that uses them, follow the announced reindexing steps, and create a new full backup before resuming incremental backups. The practical implication is to treat the server upgrade, extension rebuild and client-tool rollout as one coordinated maintenance task.

