PostgreSQL patches CVE-2026-6460 in 52-flaw update

PostgreSQL has released security updates for every supported branch, fixing 52 vulnerabilities including a long-standing flaw that can allow an authenticated database user to run code on the server. The updates, released on 12 November, cover versions 18.7, 17.12, 16.16, 15.20 and 14.25.
The headline flaw is tracked as CVE-2026-6460 and carries a CVSS score of 8.8. It is a type-confusion flaw in the way PostgreSQL handles composite types, which are types built from named fields, each with its own data type. A database user who can create objects can exploit the flaw to run code with the rights of the operating system user that runs PostgreSQL.
Security researcher Mehmet Ince described a working exploit for the flaw, demonstrated on PostgreSQL 18.6, in a technical write-up published this week. The PostgreSQL project credits more than a dozen reporters for CVE-2026-6460, including Ince, and credits him on five other flaws in the same release.
What the update fixes
The release fixes 52 flaws in total, and the project rates 32 of them at 8.8, the highest score in the release. Most of the flaws need an authenticated account, but one does not. CVE-2026-116322 lets an unauthenticated client trigger a restart of PostgreSQL 18 servers, causing a denial of service.
The project has not reported any attacks using CVE-2026-6460, and the assessment in the CVE record lists exploitation as none. That does not remove the urgency: a working exploit has been described in public, and the flaw affects all versions before the fixed releases.
Administrators should update to the fixed release that matches their major version: 18.7, 17.12, 16.16, 15.20 or 14.25. The release also includes fixes for more than 140 other bugs, and a second release candidate for PostgreSQL 19.
Extensions need updating too
This is not a routine minor release. The fix for CVE-2026-6460 changes how PostgreSQL stores composite values and how compiled extensions read them. That means extensions must be updated at the same time as the server.
Devrim Gunduz, who maintains the community RPM packages, warned that an old extension on a new server still loads and works, but because it lacks the new checks, it may not be protected from the vulnerability. Package repositories have rebuilt extensions against the new minor releases so administrators can update both together.
After updating, administrators should also follow the reindexing steps in the release announcement, which cover possibly affected GIN indexes, pg_trgm GiST indexes and B-tree indexes on bpchar columns declared without a length.
PostgreSQL 14 reaches end of life
The release also marks the end of PostgreSQL 14. Version 14.25 is its last release, and the branch will receive no further security fixes. Organisations still running PostgreSQL 14 should plan a move to a supported branch.
The PostgreSQL Global Development Group, which publishes the database releases, says there is no workaround in the advisory for servers that cannot be updated yet. The practical advice is therefore straightforward: patch the server and its extensions together, check the reindexing steps, and move off PostgreSQL 14.
Sources: The Hacker News; Brandefense.