PostgreSQL patches 52 security holes, sends version 14 into retirement
Some fixes need more than installation, while the next major release is due November 19
The PostgreSQL developers patched 52 security vulnerabilities and over 140 bugs across versions 14 to 18 in recent updates. The final release for version 14, PostgreSQL 14.25, is now unsupported and users are advised to migrate to a newer major version. Some fixes necessitate follow-up actions, such as rebuilding affected indexes or taking a fresh full backup. Administrators must refer to the release's post-update instructions.
Alastair Turner, a community technologist at Percona, emphasized the gravity of the high-severity code execution flaws, although exploiting them requires database access. He clarified that brute-force scans of the correct port would not easily uncover these vulnerabilities, as they can be exploited through SQL injection or credential theft, posing a greater risk.
One such flaw, CVE-2026-6460, is a type confusion issue that allows a database user with object creation permissions to execute arbitrary code, carrying a CVSS severity score of 8.8 out of 10.
Turner attributed the surge in security discoveries to AI-assisted scanning and heightened scrutiny as PostgreSQL gains traction in enterprise computing. He noted that this represents the highest number of CVEs fixed in a quarterly release and foresees this trend continuing. The fixes span various parts of the software, with no single code segment being broken. Instead, a broad base has been patched. This third consecutive quarterly release sets a new record for the number of CVEs addressed.
PostgreSQL 14 users now face a decision: a major-version upgrade or operating without additional security and bug fixes. Their choice may hinge on internal upgrade policies. If they opt to retain the previous major release, PostgreSQL 17 would be their target. Version 18 remains the latest generally available release until PostgreSQL 19's general availability on November 19, barring any unforeseen issues.
PostgreSQL 19 will introduce a new REPACK command, featuring a CONCURRENTLY option that allows ongoing reads and writes while reclaiming disk space.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.