PostgreSQL releases security and bug fixes for versions 14 through 18
The PostgreSQL Global Development Group has issued minor version updates across all supported branches to address security vulnerabilities and bugs.
Summary
The PostgreSQL Global Development Group has released a series of minor version updates for all currently supported database branches. These updates include versions 18.6, 17.11, 16.15, 15.19, and 14.24, which were made available in August 2026.
These releases are focused on providing critical security patches for identified CVEs and a wide array of bug fixes. Because these are minor updates within the same major version, they do not alter the on-disk data format, allowing for binary-only replacements without requiring a full database migration or data dump and restore.
Technical details of PostgreSQL minor upgrades
- Data Compatibility: Minor releases (e.g., moving from 15.13 to 15.19) share the same on-disk data format, meaning the data directory remains unchanged and tools like pg_upgrade are not required.
- Update Mechanism: On RHEL-based systems, the upgrade is performed by replacing existing binaries via package managers like dnf, which involves stopping the service, swapping binaries, and restarting.
- Security and Stability: The updates specifically target CVEs and cumulative bug fixes; users are advised to review all cumulative release notes between their current version and the target version to identify potential requirements like reindexing.
- Rollback Strategy: A safe rollback involves reinstalling previously saved RPM packages, undoing the dnf transaction, and restoring data from verified backups such as pgBackRest, pg_basebackup, or storage-level snapshots.
Why it matters
For system administrators and database engineers, these updates represent a low-risk but essential maintenance task to ensure security compliance. The ability to perform binary-only upgrades significantly reduces downtime compared to major version migrations, provided that a tested rollback plan and verified backups are in place.
What to do
- Users of PostgreSQL versions 14 through 18 should update to versions 14.24, 15.19, 16.15, 17.11, or 18.6.
- Review all cumulative release notes between your current version and the target version to identify potential requirements like reindexing.
- Take and verify a fresh backup before performing the upgrade.
- On RHEL-based systems, use the dnf update command to replace existing binaries.
Original reference: postgr.es →