← All security briefings

Attention

PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security issues; PostgreSQL 14 reaches end of life

Identifiers: CVE-2026-6460 · CVE-2026-6467 · CVE-2026-14661 · CVE-2026-16237 · CVE-2026-16240 · CVE-2026-18447 · CVE-2026-116303 · CVE-2026-116304 · CVE-2026-116306 · CVE-2026-116307 · CVE-2026-116308 · CVE-2026-116309 · CVE-2026-116310 · CVE-2026-116311 · CVE-2026-116312 · CVE-2026-116313 · CVE-2026-116314 · CVE-2026-116315 · CVE-2026-116316 · CVE-2026-116317 · CVE-2026-116318 · CVE-2026-116319 · CVE-2026-116320 · CVE-2026-116321 · CVE-2026-116322 · CVE-2026-116323 · CVE-2026-116325 · CVE-2026-116326 · CVE-2026-116327 · CVE-2026-116328 · CVE-2026-116329 · CVE-2026-116330 · CVE-2026-116331 · CVE-2026-116332 · CVE-2026-116333 · CVE-2026-116335 · CVE-2026-116336 · CVE-2026-120139 · CVE-2026-120141 · CVE-2026-120142 · CVE-2026-120143 · CVE-2026-120144 · CVE-2026-120145 · CVE-2026-120146 · CVE-2026-120147 · CVE-2026-120148 · CVE-2026-120149 · CVE-2026-120150 · CVE-2026-120151 · CVE-2026-120152 · CVE-2026-120153 · CVE-2026-120154

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

On 12 November 2026 the PostgreSQL Global Development Group released updates to all supported branches, fixing 52 security vulnerabilities and more than 140 bugs. Not every fix applies to every branch, component or configuration. 14.25 is the final PostgreSQL 14 release, so 14 is now end of life. 19 RC 2 is a release candidate for testing, not the production fix.

Classification reason: Checked 14 November 2026 against the PostgreSQL release announcement, the 16.16 release notes and the official CVE pages. Fixed versions are available for all supported branches; PostgreSQL 14 is end of life after 14.25.

Impact

Several fixed issues allow arbitrary code execution as the operating system user running the database or a client tool, but each has prerequisites. CVE-2026-120151 needs a role that can create objects and is not unauthenticated remote code execution by default. CVE-2026-120145 needs a compromised publisher and a superuser-owned subscription. CVE-2026-116314 needs a crafted non-plain archive fed to pg_restore; a patched pg_restore still does not make untrusted backup SQL safe to restore. CVE-2026-120154 lets a role with INSERT, UPDATE and applicable SELECT read rows despite row-level security without enabling improper writes. Some branches also need post-update steps, including rebuilding C-language extensions for full protection from the new composite type checks.

Who is affected

Self-hosted or containerised PostgreSQL 18, 17, 16, 15 or 14 below 18.7, 17.12, 16.16, 15.20 or 14.25; any host running pg_restore from an older release; logical replication subscribers with superuser-owned subscriptions. Managed database users depend on their provider's maintenance schedule and should confirm deployment on their instance.

Products and versions

Products and versionsAffectedFixed
PostgreSQL 18 18.x before 18.7; the 52-issue release has per-issue branch, privilege and feature conditions 18.7
PostgreSQL 17 17.x before 17.12; the 52-issue release has per-issue branch, privilege and feature conditions 17.12
PostgreSQL 16 16.x before 16.16; the 52-issue release has per-issue branch, privilege and feature conditions 16.16
PostgreSQL 15 15.x before 15.20; the 52-issue release has per-issue branch, privilege and feature conditions 15.20
PostgreSQL 14 14.x before 14.25; the 52-issue release has per-issue branch, privilege and feature conditions 14.25
PostgreSQL pg_restore client tool Versions before 18.7, 17.12, 16.16, 15.20 and 14.25 in the corresponding major line; CVE-2026-116314 18.7 / 17.12 / 16.16 / 15.20 / 14.25 in the corresponding major line

Exploitation evidence

Exploitation not established. No actual exploitation is established in the official release announcement, the CVE notices or the CISA Known Exploited Vulnerabilities catalog as of 13 November 2026. The absence of a listing is not proof the issues are unexploited.

Sources: PostgreSQL Global Development Group, CISA

Actions

  1. Update to 18.7, 17.12, 16.16, 15.20 or 14.25 using your platform's supported same-major procedure: stop the server, replace binaries, start. No dump/reload or pg_upgrade is required.
  2. Verify the actual running server version and the pg_restore and other client tool versions, not just an image tag or host package name.
  3. Rebuild C-language extensions for the new server version; do not disable the composite_type_mismatch checks, which the vendor says carries security risk.
  4. Read your exact branch's release notes and qualify conditional post-update steps (GIN, pg_trgm GiST, bpchar B-tree, TOAST, partition constraints, incremental backup baseline) before running anything.
  5. If on PostgreSQL 14, install 14.25 and plan a separate, tested major-version upgrade.
  6. Managed database users: ask the provider for the maintenance schedule and confirmation of effective deployment.

Unknowns

  • Whether any of the 52 issues is being exploited in the wild. The release announcement, the 16.16 release notes, the four CVE pages reviewed and the CISA Known Exploited Vulnerabilities catalog as of 13 November 2026 do not establish in-the-wild exploitation; absence from those sources is not proof that none is occurring.
  • Which backported package or image builds from third-party vendors contain which fixes; verify per vendor.
  • Which specific extensions require source changes rather than a rebuild; consult each extension's maintainer.

Sources

Change history

  1. — Published: 14 November 2026: briefing published following the 12 November 2026 PostgreSQL release of 18.7, 17.12, 16.16, 15.20 and 14.25, which fixes 52 security vulnerabilities and marks PostgreSQL 14 end of life.

Subscribe: RSS feed · JSON Feed · Feed format and fields