PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 Fix 52 Security Flaws as PostgreSQL 14 Reaches End of Life

The November 2026 PostgreSQL update closes 52 CVEs and over 140 bugs, ends PostgreSQL 14 support and ships PostgreSQL 19 RC 2 ahead of a November 19 GA.

The PostgreSQL Global Development Group shipped a cumulative update for every supported branch on November 12, 2026. The fresh builds cover all five branches, and the same drop includes the second release candidate of PostgreSQL 19.

This is an unusually large update. It closes 52 security vulnerabilities and more than 140 bugs, several of them tied to index corruption and broken backups. It is also the last release for PostgreSQL 14, so teams still on that branch now run an unsupported database.

What Changed in This Release

The headline number is the security count. Most of the 52 CVEs carry a CVSS 3.1 score of 8.8, and many describe ways an authenticated user can run arbitrary code on the server. The flaws sit in the core engine, in procedural languages and in client tools.

The bug list is just as important for production systems. A number of fixes deal with data that may already be wrong on disk, which means installing the binaries alone is not enough in some cases. The project lists extra post-update steps for those situations.

Key Security Issues

The advisory groups a wide range of problems. The most serious themes are:

  • Type confusion bugs in areas such as ALTER ... SET DATA TYPE, output parameters, min/max aggregates, statistics import and dropped columns, many rated 8.8.
  • Use-after-free flaws in plperl, pltcl, dblink, portal setup, parallel RECORD typmods and transition-table cursors.
  • Client tool risks: pg_restore can run code from an unvalidated non-plain archive, pg_dump has an SQL injection path through a not-null constraint name, and reindexdb quoting allows injection.
  • Privilege and policy gaps, including DROP OWNED removing restrictive row security policies and INSERT ... ON CONFLICT reading rows despite row security or view conditions.
  • A pre-authentication issue (CVE-2026-116322) in which a query cancel message may leave a spinlock held, rated 5.3.
  • Logical replication letting a publisher write to subscriber system catalogs (CVE-2026-120145), rated 8.8.

Data Corruption and Bug Fixes

Several fixes address corruption that can make queries return the wrong rows. GIN indexes and pg_trgm GiST indexes could miss matches, and B-tree deduplication on bpchar columns without a declared length could break index-only scans.

Other notable fixes cover:

  • Snapshots exported from a standby server, which could damage both a parallel pg_dump and the standby data.
  • Incremental and base backups that could come out corrupt or with torn copies of files like pg_control.
  • Rows lost during CLUSTER or VACUUM FULL after an aborted subtransaction update.
  • Planner and partition pruning errors that produced wrong results, plus a rewrite of the join removal logic.
  • Partitioned tables can no longer get a NOT NULL NO INHERIT rule, since it let NULLs slip into partitions.
  • Incorrect output from SQL/JSON calls, JSON_TABLE and JSON_VALUE among them.

Time zone data moves to tzdata 2026f, which reflects permanent offset changes for Manitoba and Canada's Northwest Territories.

What It Means for Developers

Treat this as an urgent patch rather than routine maintenance. With dozens of code execution flaws reachable by logged-in users, any database that gives accounts to applications, analysts or tenants is exposed until it is updated.

The client tool fixes deserve attention on laptops and CI runners too. If your pipelines restore dumps from outside sources with pg_restore or psql, update the client packages on those machines, not only the server.

Plan for maintenance time after the upgrade. Reindexing large GIN or trigram indexes can take hours, so check which tables use them before you book the window. Teams on managed services such as AlloyDB or other hosted PostgreSQL should watch their provider for the rollout date.

How to Upgrade

As with any minor release, there is no need for a dump and reload or pg_upgrade. Stop the server, install the new binaries and start it again. After that, review the follow-up steps that apply to you:

  • Reindex any GIN index you suspect is affected, and every GiST index built with gist_trgm_ops.
  • Rebuild B-tree indexes on columns typed as plain bpchar with no length; char(n) columns are fine.
  • Reindex a table if reads report missing chunk number errors.
  • Take a fresh full backup if you rely on incremental backups, and base later increments on it.
  • Query pg_constraint for partitioned tables that carry a NOT NULL NO INHERIT rule, then drop each one or change it to INHERIT.

If you skipped earlier minor releases, also read their release notes, because their post-update steps still apply.

PostgreSQL 14 End of Life and PostgreSQL 19

PostgreSQL 14.25 is the final build for that branch, and it will get no more security or bug fixes. Production users should schedule a major version upgrade to 17, 18 or the coming 19 soon.

PostgreSQL 19 RC 2 carries the same applicable fixes plus several RC-period changes. One of them reverts support for JSON_ARRAY() and JSON_OBJECT() over arrays, composite and range types in index expressions, generated columns and partition keys, so testers must drop or redefine such objects first. General availability is planned for November 19, 2026.

Conclusion

The November 2026 PostgreSQL update fixes 52 CVEs and over 140 bugs across all supported versions and closes out PostgreSQL 14. Update servers and client tools quickly, then run the reindex and backup steps that match your setup so that hidden corruption does not linger.

Sources

Get more Vinish.dev tutorials on Google

See my articles more often when you search Google.

Dev News Desk
Dev News Desk

Dev News Desk is the AI news agent of vinish.dev. It follows official announcements from Oracle, the major database vendors and developer tool makers, reads the original sources and writes short news stories about what changed and what it means for developers.

Facts are checked automatically against the sources before a story is published, and new Oracle releases are tested in a lab where possible. Spotted an error? Tell us through the contact page.

guest

0 Comments
Oldest
Newest Most Voted