Checked as of 14 November 2026.

On 12 November 2026 the PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25. The release announcement says this set fixes 52 security vulnerabilities and more than 140 bugs. Not every fix applies to every branch, component or configuration. Your job is to confirm the fixed version your site should run and finish the post-update steps your branch calls for. Current status lives in our briefing.

What the release means for you

  • One minor update per branch. The vendor says a same-major minor update needs no dump/reload and no pg_upgrade: stop the server, install the new binaries with your platform’s supported procedure, start it again.
  • PostgreSQL 14 is end of life. 14.25 is the final 14 release. Install it, then plan a separate, tested major-version upgrade.
  • PostgreSQL 19 RC 2 is for testing. It is not the production fix for this advisory.
  • Vendors may backport. Verify that the server you actually run and the client tools you use for backups contain the fix. A mutable image tag or a host package name alone proves nothing.
  • Managed database? Ask your provider when maintenance runs and how to confirm it took effect on your instance.

The step most people miss: extensions

The 16.16 release notes explain that new composite type version checks require rebuilding C-language extensions for full protection, and some extensions need source changes. A new server with an old extension build is not complete protection. The notes mention a composite_type_mismatch parameter that disables the checks; the vendor warns this carries security risk, so do not use it as a shortcut.

The announcement also lists conditional post-update steps, detailed in each branch’s release notes: reindex GIN indexes you suspect are corrupted, reindex pg_trgm GiST indexes using gist_trgm_ops, reindex tables showing “missing chunk number” errors, reindex B-tree indexes on bpchar columns declared without a length (char(n) is not affected), repair certain NOT NULL NO INHERIT constraints on partitioned tables, and take a new full baseline if you use incremental backups. Each applies only where that feature exists on your branch. Do not run constraint drops or mass reindexes blindly; qualify each against your schema and run it in a controlled maintenance window.

Four fixed issues, four different prerequisites

  • CVE-2026-120151: an object creator can execute code as the OS user running the database, via a reentrant domain CHECK that changes a RECORD variable’s row type during a cast. This is not unauthenticated remote code execution by default.
  • CVE-2026-120145: a compromised publisher plus a superuser-owned subscription lets logical replication write subscriber system catalogs and execute code. Only superuser-owned subscriptions are vulnerable.
  • CVE-2026-116314: a crafted non-plain archive can execute code as the OS user running pg_restore. This is a client tool fix, so patch pg_restore wherever restores run. Archive content legitimately runs SQL at the destination, so a patched pg_restore does not make an untrusted backup safe.
  • CVE-2026-120154: an attacker with INSERT, UPDATE and applicable SELECT privileges can read every row despite row-level security through iterated INSERT … ON CONFLICT DO UPDATE. It enables reading, not improper writes, and is distinct from CVE-2026-16237.

All four are fixed in 18.7, 17.12, 16.16, 15.20 and 14.25; for CVE-2026-116314 that floor applies to the pg_restore version itself. The official release and CVE notices, and the CISA Known Exploited Vulnerabilities catalog as of 13 November 2026, establish no in-the-wild exploitation. Absence is not proof. Update promptly without assuming your instance is compromised.

Worked example: a small shop app from 16.15 to 16.16

Hypothetical: a small online shop runs PostgreSQL 16.15 from a vendor container image, uses pg_trgm with GiST indexes for product search, and loads one third-party C-language extension. Nightly logical dumps are restored by pg_restore on a staging host.

  1. Recovery first. Prove the latest backup restores on staging before touching production. A green backup job is not a working backup; a completed test restore is. Keep the 16.15 image reference and a fresh pre-update backup so a rollback path exists. See our backup strategy guide.

  2. Qualify the inputs. Pick a vendor image whose contents are 16.16 with pg_trgm rebuilt for 16.16. Confirm the third-party extension has a 16.16-compatible build or documented source changes. Update pg_restore on staging to 16.16 too.

  3. Plan the restart. Announce a short window. Stop the server, switch to the new image, start it. This stays on major 16; nothing moves to 19 automatically.

  4. Verify what runs. Compare the server’s reported version with the image’s immutable digest, then check the client tool:

    SELECT version();
    pg_restore --version

    A version string proves the release is activated. It does not prove absence of compromise or that every role’s permissions are correct.

  5. Check normal flows. The app connects, users log in, read-write jobs finish, and a regression pass on search and checkout succeeds. See our monitoring guide.

  6. Finish branch steps. Reindex the gist_trgm_ops indexes per the 16.16 notes. Check for bpchar-without-length columns and partitioned tables; this schema has none, so those steps are recorded as not applicable. PostgreSQL 16 has no built-in incremental backup feature, so the new full baseline advice does not apply through PostgreSQL itself; follow your backup tool’s own guidance.

Rollback limits. Within major 16 the data format is compatible, but do not blindly start an older binary on a data directory that has since changed. If rollback is needed, use the retained image and the pre-update backup through your vendor’s supported procedure.

Acceptance criteria

Done means: the running server reports a fixed version; every C-language extension is built for that version; backup and restore tools report a fixed version; branch-specific post-update steps are completed or documented as not applicable; a restore test passed after the update; and, if you were on 14, a dated major-upgrade plan exists.