Skip to content
ThreatCluster

PostgreSQL 18.7 and 14.25 Releases Address Index Corruption Bugs

First seen 14 Nov 2026, 11:44 UTC •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 14, 2026 at 11:45 UTC
  • •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.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 12h ago How this analysis works

Timeline

2026-11-12
CVE disclosures for PostgreSQL vulnerabilities
Multiple CVEs published, including CVE-2026-116326 and CVE-2026-116304, affecting versions 14.25 and 18.7.
PostgreSQL.org
2026-11-12
CVE-2026-116326 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-11-12
CVE-2026-116304 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE

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?
Versions 14.25 and 18.7 are affected, with earlier versions also needing attention.
What should I do if I use incremental backups?
It is recommended to take a new full backup after upgrading, as existing incremental backups may be corrupt.
Are these vulnerabilities being actively exploited?
No active exploitation has been reported; however, users should apply the updates promptly.