Published
PostgreSQL Security Update (November 2026): Versions, CVE-2026-6460 and What to Do
PostgreSQL released updates for every supported version on November 12, 2026. Here is what changed and what admins should do.
1. The new versions
18.7, 17.12, 16.16, 15.20 and 14.25. The PostgreSQL project says the release fixes over 140 bugs.
https://www.postgresql.org/download/
2. The security fixes
The Hacker News reports 52 security fixes, including CVE-2026-6460 (CVSS 8.8), a type confusion flaw rooted in a 2004 change. A database user who can create objects could run code as the PostgreSQL operating system user. No attacks have been reported.
3. PostgreSQL 14 is end of life
14.25 is the final release. Plan an upgrade to a supported major version.
https://www.postgresql.org/support/versioning/
4. After updating
Rebuild or update C-language extensions, update client tools such as pg_dump on every machine, and reindex affected GIN, pg_trgm GiST and bpchar B-tree indexes.
REINDEX INDEX your_index_name;
5. Backups
If you use incremental backups, take a new full backup after updating.
Sources
PostgreSQL Global Development Group release announcement (November 12, 2026); The Hacker News, November 13, 2026.
FAQ
Is there a workaround?
The Hacker News says the advisory offers none for servers that cannot update yet. Update as soon as you can.
Do I need pg_upgrade?
No. Minor releases only need the new binaries and a restart.