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.
- Organizations that require the previous major release, known as N-1, would currently target PostgreSQL 17, Turner noted.
- PostgreSQL 19 is scheduled for general availability on Thursday, November 19, barring further problems.
PostgreSQL 14 users now face a major-version upgrade or running without further security and bug fixes.
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.
- "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.
- 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.
- 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.
- Version 18 remains the latest generally available release until 19 arrives.
- Users are advised to move to a newer major version.
How this summary was made: extractive summary — built from the sources' own reporting. It is drawn only from the reporting of the sources listed below — read the originals for full detail. How we summarize →