PostgreSQL fixes 52 vulnerabilities, ends version 14 support
PostgreSQL fixes 52 vulnerabilities; learn which indexes, backups and extensions need attention and what changed in version 19 RC 2.
The PostgreSQL Global Development Group on November 12 released versions 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 security vulnerabilities and more than 140 bugs. It also released PostgreSQL 19 RC 2, the second release candidate for the next major version.
Operators face more than a routine binary update: some indexes need rebuilding, existing incremental backups may be corrupt, and 14.25 is the final PostgreSQL 14 release. The project says version 14 will receive no further security or bug fixes; its users should plan a move to a supported major version.
Among the fixes, CVE-2026-6460 addresses type confusion after a data-type change that can execute arbitrary code. It has a CVSS 3.1 score of 8.8. Another 8.8 issue, CVE-2026-116314, concerns code execution through insufficient validation of non-plain archives in pg_restore. The project also fixed SQL injection in pg_dump and reindexdb. Overall, 32 of the CVEs score 8.8, according to Help Net Security.
The bug fixes include a standby snapshot problem that could corrupt both a parallel dump and standby data, and planner and partition-pruning errors that could return wrong results or miss rows. The 18.7 release notes also say full protection against the composite-type flaw requires rebuilding C-language extensions; some need source changes.
For the minor updates, PostgreSQL says to stop the server, update the binaries and restart; a dump and reload or pg_upgrade is not required. Update client tools too. Afterward:
- Reindex suspected corrupt GIN indexes, all
pg_trgmGiST indexes usinggist_trgm_ops, and B-tree indexes onbpcharcolumns declared without a length;char(n)is unaffected. For example, use:
sql REINDEX INDEX your_index_name;
- If a table produces a “missing chunk number” error, run
REINDEX TABLEon it to rebuild its TOAST index. Take a new full backup and base subsequent incremental backups on it. - Check partitioned tables for
NOT NULL NO INHERITconstraints and repair or remove affected constraints using the announcement’s query and instructions. Review earlier release notes if you skipped updates.
PostgreSQL 19 RC 2 includes applicable fixes and reverses support for certain JSON_ARRAY() and JSON_OBJECT() expressions in indexes, generated columns and partition keys: testers must drop or redefine affected objects before upgrading. Moving from an earlier major version requires a major-upgrade method, and some text-search indexes may need reindexing. General availability is planned for November 19, subject to change.
Comments ()