Minor PostgreSQL releases are usually routine: install the package, restart, done. This one isn’t. On November 12, 2026, the PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25 (plus 19 RC 2), fixing 52 security vulnerabilities and more than 140 other bugs. The headline fix, CVE-2026-6460, changes how the server stores composite values, which breaks the binary interface for C extensions.
Who can exploit what
pganalyze’s Lukas Fittl sorted the 52 CVEs by what an attacker needs. His summary: if anyone other than you can run SQL on the database, including through SQL injection, upgrade now. Any SQL user may be able to work up to the operating-system account or the superuser.
- No login needed: CVE-2026-116322 (PostgreSQL 18 only). A cancel request sent before login, timed so that
authentication_timeoutfires during cancel handling, leaks a spinlock and restarts the whole server. - Any database user: heap overflows in tsvector functions (CVE-2026-116315, CVE-2026-116317), a use-after-free on anonymous
RECORDtypes in parallel query (CVE-2026-116304), type confusion in set-returning functions such asjson_populate_recordset()(CVE-2026-120141) and integer wraparounds (CVE-2026-120139, CVE-2026-116328). - Anyone who can create objects, which includes temporary objects in
pg_tempthat any user can create by default: CVE-2026-6460 and a group of related type-confusion and use-after-free bugs. - Users with CREATE on the database: CVE-2026-6467 (CVSS 7.2). Rename a trusted extension’s schema, or target
"$user", andCREATE/ALTER EXTENSIONruns your SQL as the bootstrap superuser. - PL/Perl and PL/Tcl, if installed: several use-after-free and type-confusion bugs (CVE-2026-116307, -116319, -116320, -116309, -116326, -116323). Trusted languages are open to
PUBLICby default. - Client tools:
pg_dump,pg_restore,reindexdbandvacuumdbget fixes for SQL injection and code execution (for example CVE-2026-116314 and CVE-2026-116318). A malicious dump or a hostile database owner can attack the person running maintenance.
CVE-2026-6460: 22 years of stale row values
The official advisory explains that PostgreSQL “had inadequate tracking of typed values, and values were not self-identifying.” When a row type changes after a query has already captured values of that type, the server reads those old values with the new layout. You can trigger it with ALTER TABLE ... SET DATA TYPE, with ALTER TYPE ... ALTER ATTRIBUTE ... TYPE, or with ALTER TABLE ... ADD COLUMN followed by a rollback and another ADD COLUMN. pganalyze notes that it works within a single session, for example with a prepared statement, with no race needed, and that a proof of concept is available. The flaw dates back about 22 years. The release notes credit several reporters, including Claude and Ada Logics.
Why the fix breaks extensions
Commit 245eb832f adds version tracking to composite types. As Devrim Gündüz, who maintains the PGDG RPM packages, explains, DatumGetHeapTupleHeader() changes from a macro to a server function, and heap_getattr() now calls a new heap_datum_check(). Extensions compile those headers into their own binaries, which causes two problems:
- An old extension on a new server still loads and runs, but it doesn’t have the new checks, so it may still be exploitable. That’s why PGDG rebuilt every extension package against the new minors.
- Some extensions need code changes, not just a rebuild. pgrx shipped v0.19.4 for the new API, and PostGIS has edge cases with
pg_upgrade.
There’s also an ordering problem. If the extension packages are updated while the old server binary is still running (or the reverse), loading a library can fail:
ERROR: could not load library "/usr/lib/postgresql/18/lib/plpgsql.so":
undefined symbol: heap_datum_update_type
In pganalyze’s tests, PGDG Debian packages handled this cleanly: stop, replace, start. With RPMs, the binaries were replaced before the restart, which leaves a short window where things can break.
What to do
- Inventory C extensions on every cluster (
SELECT * FROM pg_extension;) and confirm each has a build for the new minor. pgrx-based extensions need pgrx 0.19.4 or later. - Upgrade the server and all extension packages in one maintenance window, then restart immediately. If you use Patroni or custom service units, test this in staging first.
- Managed Postgres (RDS, Cloud SQL, Azure, Supabase, Neon and others): check that your provider has rolled out 18.7/17.12/16.16/15.20/14.25, and find out how it handles custom extensions.
- Until you’re patched: revoke
CREATEon databases from roles that don’t need it, removeplperl/pltclwhere nobody uses them, and treat any app with possible SQL injection as a path to OS-level code execution. - Run
pg_dump/pg_restorefrom the new client binaries, especially on dumps you didn’t create yourself.
PostgreSQL 14 is still covered by this release. Teams on 13 or older get none of these fixes.