PostgreSQL patches 52 vulnerabilities in a five-branch release
Versions 18.7, 17.12, 16.16, 15.20 and 14.25 all shipped the same day. The worst flaw, rated 8.8, lets a type confusion bug in ALTER ... SET DATA TYPE run arbitrary code.
PostgreSQL released coordinated updates across every supported branch on 12 November: 18.7, 17.12, 16.16, 15.20 and 14.25, alongside release candidate 2 for the still-unreleased PostgreSQL 19.
The release fixes 52 security vulnerabilities, on top of more than 140 other bug fixes. Several of the security issues share the top CVSS v3.1 score of 8.8, including a type confusion flaw where running ALTER ... SET DATA TYPE lets an attacker execute arbitrary code. The advisory lists other 8.8-rated bugs touching plperl, composite types and tsvector_delete(). This is also the final release for the 14 branch, which is now end of life and will not get another patch of any kind, security or otherwise.
Why it matters: Postgres sits under a huge share of production backends, and a single-day release across five branches means almost nobody running it is exempt from checking their version. If you are still on 14, there is no 14.26 coming, so this release is the last safety net before you are on your own.
SELECT version();
The caveat: PostgreSQL 19 itself stays at RC2, general availability is still planned for 19 November, so none of these fixes change anything for people already testing it.