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 …
You're reading a preview. The full article is published by The Register on their website.
Read the full story on The Register

