---
title: 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 | ctxsec
url: https://ctxsec.com/items/postgresql-nov-12-2026-52-cves-cve-2026-6460-type-confusion-rce-18-7-17-12-16-16
description: "PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 (Nov 12) fix 52 CVEs and over 140 bugs. The headline is CVE-2026-6460 (CVSS 8.8): stale typed values left behind after ALTER ... SET DATA TYPE (and other DDL routes) can be read as the wrong type, letting a user who can create objects run arbitrary code as the operating system user running the database. Many more in the release are rated 8.8 for code execution, including type confusions, use-after-frees in PL/Perl, PL/Tcl and dblink, and client-tool bugs where a crafted archive makes pg_restore run code (CVE-2026-116314) or pg_dump tar output lets a compromised source server inject psql commands (CVE-2026-116330). One server bug needs no login: CVE-2026-116322 (5.3), where a pre-authentication cancel request can leak a spinlock. Researcher Mehmet Ince published a write-up with a working exploit on 18.6, says he could trigger the crash as the lowest-privileged login role, and dates the bug to a May 2004 commit; he shared proofs of concept with AWS, Microsoft, Google, Supabase and other managed providers in August. PostgreSQL 14 is now end-of-life."
status: "official (PostgreSQL release announcement and CVE-2026-6460 advisory, Nov 12, 2026); no exploitation reported"
published: 2026-11-13
---

> PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 (Nov 12) fix 52 CVEs and over 140 bugs. The headline is CVE-2026-6460 (CVSS 8.8): stale typed values left behind after ALTER ... SET DATA TYPE (and other DDL routes) can be read as the wrong type, letting a user who can create objects run arbitrary code as the operating system user running the database. Many more in the release are rated 8.8 for code execution, including type confusions, use-after-frees in PL/Perl, PL/Tcl and dblink, and client-tool bugs where a crafted archive makes pg_restore run code (CVE-2026-116314) or pg_dump tar output lets a compromised source server inject psql commands (CVE-2026-116330). One server bug needs no login: CVE-2026-116322 (5.3), where a pre-authentication cancel request can leak a spinlock. Researcher Mehmet Ince published a write-up with a working exploit on 18.6, says he could trigger the crash as the lowest-privileged login role, and dates the bug to a May 2004 commit; he shared proofs of concept with AWS, Microsoft, Google, Supabase and other managed providers in August. PostgreSQL 14 is now end-of-life.

[← Cybersecurity News](/news) · [markdown](/items/postgresql-nov-12-2026-52-cves-cve-2026-6460-type-confusion-rce-18-7-17-12-16-16.md)

official (PostgreSQL release announcement and CVE-2026-6460 advisory, Nov 12, 2026); no exploitation reported

2026-11-13 7:41 PM ET

### 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)](https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/) · [PostgreSQL security advisory: CVE-2026-6460](https://www.postgresql.org/support/security/CVE-2026-6460/) · [Mehmet Ince: How I ended up turning a 22-year-old PostgreSQL type confusion primitive into RCE (CVE-2026-6460)](https://mehmetince.net/part-3-6-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](https://access.redhat.com/security/cve/cve-2026-6460) · [The Hacker News: PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE (Nov 13, 2026)](https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html)
