PostgreSQL fixes 52 security flaws in one release, led by CVE-2026-6460: a 22-year-old type confusion that lets an object creator run code on the server
- Do now: update to 18.7, 17.12, 16.16, 15.20 or 14.25 and rebuild or update C-language extensions at the same time (see tip).
- Prioritize: servers where untrusted or semi-trusted users have login roles that can create objects (multi-tenant, SaaS, analytics, dev/test shared with production data).
- Clients too: update pg_dump, pg_restore, psql, reindexdb and vacuumdb wherever they run; don't restore archives from untrusted sources on old tools.
- Managed Postgres: check your provider's notes; the write-up doesn't give each service's patch status.
- No workaround is given in the advisory. The release also fixes GIN, pg_trgm GiST and bpchar index corruption and incremental-backup bugs, so follow the reindex and new-full-backup steps in the announcement.
Sources: PostgreSQL: 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2 Released (Nov 12, 2026) · PostgreSQL security advisory: CVE-2026-6460 · Mehmet Ince: How I ended up turning a 22-year-old PostgreSQL type confusion primitive into RCE (CVE-2026-6460) · Red Hat CVE page: CVE-2026-6460 · The Hacker News: PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE (Nov 13, 2026)