The PostgreSQL Global Development Group has issued a comprehensive security update addressing 52 distinct vulnerabilities across multiple supported versions of its database software. The patches, released on November 12, apply to versions 18.7, 17.12, 16.16, 15.20, and 14.25. In addition to these security fixes, the update resolves more than 140 non-security bugs, marking a significant maintenance milestone for the platform.
The vulnerabilities primarily involve memory errors and type confusion flaws, which could potentially lead to arbitrary code execution. These issues are distributed across several core components and extensions, including PL/Perl, PL/Tcl, parallel query processing, logical replication, dblink, statistics import, and various text search functions such as ts_rank_cd(). Among the 52 identified CVEs, 32 have been assigned a CVSS score of 8.8, representing the highest severity level in this release. The lowest-rated vulnerability, involving a bypass of the EXECUTE privilege on cast functions, carries a CVSS score of 3.1.
Client-side tools bundled with PostgreSQL were also found to be susceptible to exploitation. The pg_dump utility contained a SQL injection vulnerability related to not-null constraint names, while its tar-format restore script was found to be vulnerable to psql command injection. Additionally, the reindexdb tool was identified as having a flaw in how it handles the quoting of index names. The project developers advise that administrators must update both server software and client binaries, particularly in environments where multiple users have the ability to create and name database objects.
Post-patch maintenance is required for several specific database structures to ensure ongoing integrity. Administrators are instructed to perform a reindex on GIN indexes suspected of corruption, as well as on pg_trgm GiST indexes utilizing gist_trgm_ops and B-tree indexes on bpchar columns that lack an explicit length. Furthermore, any tables reporting "missing chunk number" errors must be addressed using the REINDEX TABLE command.
Due to the nature of the resolved bugs, there is a risk that existing backups may be compromised. The development group recommends that administrators currently utilizing incremental backups perform a new full backup immediately after applying the patches. Future incremental backups should then be based on this new full backup to avoid carrying over potential corruption.
This release marks the formal end of life for PostgreSQL 14. Version 14.25 is the final update for this branch, and it will no longer receive security patches or bug fixes. Organizations still operating on version 14 are urged to develop a migration strategy to transition to a newer, supported release of the software.
Simultaneously, the project has released the second release candidate for PostgreSQL 19, with general availability scheduled for November 19. Users who have been testing the version 19 release candidates should be aware that the latest build reverts support for JSON_ARRAY() and JSON_OBJECT() when used over arrays, range types, and composite types in partition keys, generated columns, and expression indexes. Any database objects currently utilizing these configurations must be redefined or dropped before upgrading to the final version of PostgreSQL 19.





