The PostgreSQL Global Development Group released PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 on 12 November, fixing 52 security vulnerabilities and over 140 bugs. It is also the final release of PostgreSQL 14, which is now end-of-life.
According to the project’s release announcement, 32 of the 52 vulnerabilities carry a CVSS 3.1 score of 8.8. The project describes 25 of them as flaws that execute arbitrary code. One of them, CVE-2026-6460, is a type confusion triggered when a column’s data type is changed, which the project says lets an object creator run arbitrary code as the operating system user running the database. The PostgreSQL YUM repository says compiled extensions have been rebuilt against the new releases, because extensions built against earlier releases may not be protected from the vulnerabilities fixed in this one. The rebuilt extensions now require at least the November minor release of their major version.
The update also fixes GIN and pg_trgm GiST index corruption and incremental backup bugs. The project recommends reindexing affected indexes and taking a new full backup after updating, to use as the base for later incremental backups.
In our reading, the risk sits with whoever can create objects in a database: application roles, analysts with schema rights, and tenants on shared clusters. Patch those servers first, update extensions in the same change window rather than leaving them on old builds, and put any remaining PostgreSQL 14 instances on an upgrade plan now that fixes have stopped. Our earlier coverage reported PostgreSQL closing a 12-year-old privilege gap in September, and this week Apache HTTP Server 2.4.71 fixed a critical mod_http2 flaw.