CVE-2026-6460 is the centrepiece of the security update the PostgreSQL Global Development Group published on 12 November 2026 for every supported version. The type-confusion flaw lets an object creator run arbitrary code with the privileges of the operating-system user that runs the database. Together with 51 other fixed vulnerabilities and more than 140 bug fixes, the update is unusually large. PostgreSQL 14 also reaches the end of its life with version 14.25.
CVE-2026-6460: Type confusion after ALTER SET DATA TYPE
According to the project’s CVE write-up, the server had inadequate tracking of typed values, and those values were not self-identifying. Stale type information could appear in data-dictionary entries, PL/pgSQL variables and many other parts of the system. The primary attack route is ALTER ... SET DATA TYPE. Other data-definition routes exist, such as the sequence ALTER TABLE ... ADD COLUMN, a rollback, and then ALTER TABLE ... ADD COLUMN again.
The score is CVSS v3.1 8.8 (vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). An attacker must be logged in as an object creator, but no further interaction from a victim is required. Any code that runs this way has the rights of the operating-system user that runs PostgreSQL — typically the instance service account, not necessarily root. All releases before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected.
The fix (commit 245eb832f) adds versions for composite types and changes how such values are stored. That has consequences for extensions: the former macro DatumGetHeapTupleHeader() is now a function in the server, and heap_getattr() calls the new check heap_datum_check(). This interface change is why the server and its extensions have to be updated together.
52 security flaws in a single update
The official announcement of 12 November lists 52 closed vulnerabilities. Thirty-two of them carry a CVSS score of 8.8, two score 8.1 and three score 7.2. Other highly rated cases include:
- CVE-2026-18447: output-parameter type confusion leading to code execution (8.8)
- CVE-2026-14661:
dblinkand replication subscriptions can append to arbitrary files (8.1) - CVE-2026-6467: extension-script schema mishandling executes arbitrary SQL (7.2)
- CVE-2026-116314:
pg_restoreexecutes code because non-plain archives were not validated (8.8) - CVE-2026-116318: a not-null constraint name in
pg_dumpallows SQL injection (8.8) - CVE-2026-120145: logical replication can write to subscriber system catalogs and thereby execute code (8.8)
- CVE-2026-116322: a pre-authentication cancel request can leak a spinlock (5.3)
Several flaws affect the scripting languages plperl and pltcl as well as utilities such as pg_dump, pg_restore, vacuumdb and reindexdb. The pre-authentication cancel request (CVE-2026-116322) is the only pre-login case on the list; it scores 5.3 and does not lead to code execution. The announcement does not report active exploitation of CVE-2026-6460 or of the other issues.
Why the server and extensions must be updated together
Operators who use packages from the PGDG RPM repositories must update the server and every compiled extension in the same transaction. Package maintainer Devrim Gündüz spells this out in a post dated 12 November. The repositories rebuilt every extension against the new minor releases. An old extension still loads on a new server, but it does not contain the checks from the fix and therefore may not be protected. A new extension on an old server looks for functions the older binary does not have and fails with “undefined symbol”.
From this release on, compiled extensions require at least today’s minor of their major version, not merely the major version. Holding the server back with a version lock or an exclude list also blocks the new extensions. Updating only the server and holding the extensions back leaves old libraries in place without the new checks. Anyone who runs PostgreSQL outside the default systemd unit, for example under Patroni, must restart the service after the package change; otherwise the old binary keeps running.
The announcement also recommends reindexing after the update: GIN indexes that may have been affected by the fixed corruption bugs, pg_trgm GiST indexes that use the gist_trgm_ops operator class, and B-tree indexes on bpchar columns declared without a length (char(n) columns are not affected). If a table shows missing chunk-number errors after an earlier REINDEX CONCURRENTLY on a TOAST table, that table should be reindexed. Operators who use incremental backups should take a new full backup after the update and base later incrementals on it. For partitioned tables, the announcement supplies a query that finds NOT NULL NO INHERIT constraints; unwanted ones can be dropped with ALTER TABLE ... DROP CONSTRAINT, wanted ones repaired with ALTER CONSTRAINT ... INHERIT. The second command fails if any partition already contains NULL values in that column.
Other fixes and the end of PostgreSQL 14
Besides the security flaws, the update fixes more than 140 bugs. Several of them can cause data loss or inconsistency after a crash, including a checkpoint that starts while a multixact is being created or while a prepared transaction is being aborted. State files of pending prepared transactions are now written atomically. Further fixes cover GIN and pg_trgm indexes, incremental and base backups, the planner’s join-removal implementation, partition pruning, logical replication and standby servers. Time-zone data matches tzdata 2026f.
PostgreSQL 14 reaches the end of its life with version 14.25. There will be no further security or bug fixes. Older major versions are also affected by the flaws but receive no update. Anyone still running 14 or older in production needs a plan to move to a supported version. The same day also brings the second release candidate of PostgreSQL 19; general availability is planned for 19 November 2026, unless another candidate is required.
What operators should do now
A dump and restore or a run of pg_upgrade is not required for this minor update. The service is stopped, the binaries are replaced, and the service is started again. The order of work still matters:
- Install the matching release: 18.7, 17.12, 16.16, 15.20 or 14.25, depending on the major version.
- Update or rebuild every C-language extension in the same step, including PostGIS and other out-of-tree packages.
- After startup, review the recommended reindex steps, especially for GIN, pg_trgm and length-less
bpchar. - If you use incremental backups, take a new full backup.
- On partitioned tables, search for
NOT NULL NO INHERITconstraints; the announcement includes a query for that. - Move PostgreSQL 14 instances to a supported version without delay.
The scale is reminiscent of other bundled updates in recent weeks, such as the Next.js security release on cache flaws and the fixes for CVE-2026-123488 in Craft CMS. Anyone using PostgreSQL-compatible cloud services should also keep the earlier case CVE-2026-119923 in Babelfish for Aurora PostgreSQL in mind — it affects a compatibility layer, not the core server.




