PostgreSQL update fixes 52 vulnerabilities, 32 rated 8.8, and ends support for version 14
The PostgreSQL Global Development Group shipped an update to every supported branch on 12 November: 18.7, 17.12, 16.16, 15.20 and 14.25, together with the second release candidate of PostgreSQL 19. The announcement lists 52 security vulnerabilities and more than 140 bug fixes, and it is also the last release of PostgreSQL 14, which is now end-of-life and will get no further security or bug fixes.
By the CVSS scores in the announcement, 32 of the 52 vulnerabilities are rated 8.8, and most of those are described as allowing arbitrary code execution. The recurring classes are type confusion, for example after ALTER with SET DATA TYPE, in output parameters, in min and max aggregates, in statistics import and in plpgsql record fields, and use-after-free bugs in parallel record handling, portal setup, transition-table cursors and dblink. The procedural languages feature heavily: several plperl issues, a pltcl use-after-free and a plpgsql type confusion. Two heap buffer overflows sit in text search functions, tsvector_delete and ts_rank_cd.
Some of the most practical items are in the client tools. pg_restore could execute code because non-plain archives were not validated, a tar-format restore script failed to block psql command injection, a not-null constraint name allowed SQL injection in pg_dump, reindexdb quoted index names unsafely, and vacuumdb with the missing-stats-only option let a database owner run code as the user running vacuumdb. Restoring a dump from an untrusted source was a risky operation before, and these fixes show why.
The update also carries data-integrity fixes that need action after installing. The announcement asks users to reindex pg_trgm GiST indexes, which could miss matching rows, B-tree indexes on bpchar columns without a declared length, where index-only scans could return wrong results, and TOAST indexes rebuilt with REINDEX CONCURRENTLY if missing chunk errors have appeared. After several fixes to incremental backup, it recommends taking a new full backup and building later incrementals on it. NOT NULL NO INHERIT constraints on partitioned tables are now refused in all cases, with instructions for finding affected tables.

Why it matters
This is a large security release, and the end of PostgreSQL 14 turns it into a deadline: anyone still on 14 has received the last fix. For everyone else the update is not only a package bump, since the reindex and full-backup steps are part of applying it correctly.