PostgreSQL 18.7 and 14.25 Releases Address Index Corruption Bugs
Article Content
- •PostgreSQL 18.7 and 14.25 address critical index corruption vulnerabilities.
- •Users must reindex affected indexes and take new full backups post-upgrade.
- •Incremental backups may be corrupt; full backups are recommended.
On November 12, 2026, multiple CVEs were published affecting PostgreSQL versions 14.25 and 18.7. The vulnerabilities, including CVE-2026-116326, CVE-2026-116304, and others, could lead to index corruption, impacting database integrity. Users are advised to reindex affected indexes and take new full backups after upgrading. The 18.7 release introduces defenses against issues arising from altering composite types concurrently with data operations. Existing incremental backup files should not be trusted due to potential corruption. Users of versions earlier than 18.6 and 14.24 are also urged to review migration instructions. The updates are for maintaining database reliability and security.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Following this threat?
Track CVE-2026-116303 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.
Free account · no card needed
Common questions
Which PostgreSQL versions are affected?
What should I do if I use incremental backups?
Are these vulnerabilities being actively exploited?
Continue Reading
PostgreSQL Releases Updates Fixing 52 Vulnerabilities as Version 14 Reaches EOL PostgreSQL has released updates for versions 14.25, 15.20, 16.16, 17.12, and 18.7, addressing 52 security vulnerabilities and over 140 bugs. This includes the second release candidate for PostgreSQL 19. Version 14.25 is the final release for version 14, which is now end-of-life and will no longer receive security…