
The PostgreSQL Global Development Group released updates on November 12 for all supported versions, fixing 52 security vulnerabilities and more than 140 other bugs. The one drawing attention is CVE-2026-6460 (CVSS 8.8), a type confusion flaw: after a column’s data type is changed with ALTER ... SET DATA TYPE, the server can still hold older values and read them as the new type. The project says this lets an object creator run arbitrary code as the operating system user that runs the database.
The Hacker News reports that researcher Mehmet Ince published a technical write-up this week showing a working exploit on PostgreSQL 18.6. The write-up includes the SQL for a crash and a memory-leak step but not the final command-execution step. Ince traces the underlying behavior to a 2004 change that allowed column types to be altered. Neither the project’s advisory nor Red Hat, per The Hacker News, says whether an account with only default privileges can go beyond the crash; Red Hat describes the attacker as someone with a login and the ability to create or modify objects. Neither The Hacker News nor the project’s advisory reports any attacks.
The release is larger than that one flaw. The announcement lists 52 CVEs. Many are rated 8.8, including use-after-free and buffer-overflow bugs in the PL/Perl, PL/Tcl and text-search components, and pg_restore and pg_dump issues in the client tools. The Hacker News singles out CVE-2026-116322, a pre-authentication cancel request that can restart PostgreSQL 18 servers, as the only server flaw in its reading of the scores that needs neither a login nor any user action. The PostgreSQL announcement rates that one CVSS 5.3 and describes it as a spinlock leak. Our September post covered a different PostgreSQL flaw, CVE-2026-6471.
How to check if you’re affected
Affected versions are every PostgreSQL release before 18.7, 17.12, 16.16, 15.20 and 14.25, per the project’s advisory for CVE-2026-6460. To see what you run (our suggestion, not from the sources), use SELECT version(); or postgres --version and compare against your major version.
- Update the server to the matching fixed release. The project says this is a cumulative minor release, so no dump and reload or
pg_upgradeis needed. - Update extensions too. The PostgreSQL RPM repository says extensions built against older releases still load but may not be protected, and its rebuilt extension packages now require the new minor release. On RHEL-family systems, updating a single extension also updates the server and restarts the PostgreSQL service, so plan for that. The repository notes that extensions built against the new release fail to load on older minor releases, and some extensions need source changes, according to The Hacker News.
- If PostgreSQL runs outside its package’s own service unit, for example under Patroni, The Hacker News quotes an RPM maintainer saying to restart it right after updating.
- Update client tools such as
pg_dump,pg_restore,reindexdbandvacuumdbon every machine that runs them. - Do not use the new
composite_type_mismatchsetting to turn the new checks off; The Hacker News says the project warns it carries security risks. - There is no workaround for servers that cannot be updated, per The Hacker News’s reading of the advisory and release notes.
- PostgreSQL 14 is now end-of-life, and 14.25 is its last release. The announcement says users on 14 should plan an upgrade to a supported version.
- After updating, the announcement lists follow-up steps: reindex a GIN index you suspect is affected; reindex GiST indexes that use
gist_trgm_opsif you usepg_trgm; reindex B-tree indexes onbpcharcolumns declared without a length; and take a new full backup if you use incremental backups. Users who skipped earlier minor releases may need steps from those releases’ notes.
Researcher Ince says he shared proofs of concept with the security teams of managed PostgreSQL providers including AWS (Aurora and RDS), Microsoft, Google (AlloyDB), Supabase, Databricks and Ubicloud in August, per The Hacker News. The write-up does not give each service’s current patch status, so check your provider’s own notices.
Sources
- PostgreSQL: CVE-2026-6460, type confusion after ALTER … SET DATA TYPE executes arbitrary code
- PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released
- PostgreSQL YUM Repository: Extensions are rebuilt against the November 2026 minor releases
- Mehmet Ince: Part 3/6, turning a 22-year-old PostgreSQL type-confusion primitive into RCE (CVE-2026-6460)
- The Hacker News: PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
