PostgreSQL patches 52 security holes, sends version 14 into retirement
PostgreSQL developers have patched 52 security vulnerabilities and more than 140 bugs in updates spanning versions 14 to 18, alongside a second release candidate for version 19.
The batch includes PostgreSQL 14.25, the final release for the now-unsupported version 14. Users are advised to move to a newer major version.
Some fixes also require follow-up work, including rebuilding affected indexes or taking a fresh full backup. Administrators should check the release's post-update instructions.
Alastair Turner, community technologist at open source consultancy Percona, said the high-severity code execution flaws should be taken seriously, although exploiting them requires database access.
"This isn't something just a brute-force scan of the right port is going to find," he said. "They can make compromises through SQL injection or credential theft a lot worse, but don't create the opportunity for remote, anonymous code execution."
Among the fixes is CVE-2026-6460, a type confusion flaw that could let a database user with permission to create objects execute arbitrary code. It carries a CVSS severity score of 8.8 out of 10.
Turner attributed the growing number of security discoveries partly to AI-assisted scanning and partly to increased scrutiny as PostgreSQL gains ground in enterprise computing.
"It is a record number of CVEs fixed in a quarterly release, and I don't think we've seen the end of that trend. Looking down the list of where these CVEs came from, we see Anthropic and OpenAI open source scanners, so it is clear AI or brute force is playing a role," he said.
Turner said the fixes spanned multiple parts of the software. There "isn't one piece of code that was broken" but rather "a wide base that got patched."
"It's also worth noting that this is the third quarterly release in a row which sets a new record for the number of CVEs patched," he added.
PostgreSQL 14 users now face a major-version upgrade or running without further security and bug fixes. Their destination may depend on internal upgrade policies. Organizations that require the previous major release, known as N-1, would currently target PostgreSQL 17, Turner noted. Version 18 remains the latest generally available release until 19 arrives.
PostgreSQL 19 is scheduled for general availability on Thursday, November 19, barring further problems. It is set to include a new REPACK command, whose CONCURRENTLY option allows reads and writes to continue while disk space is reclaimed. VACUUM FULL requires an exclusive table lock, blocking reads and writes while it runs. (R)