PostgreSQL 14.25 is the final 14 release, with 52 security fixes
PostgreSQL 14.25, issued on 12 November 2026, is the last release of that version, which is now end-of-life. The same update delivered 18.7, 17.12, 16.16, 15.20 and a second PostgreSQL 19 release candidate, fixing 52 security vulnerabilities and over 140 bugs.
PostgreSQL Global Development Group on 12 November 2026 released 18.7, 17.12, 16.16, 15.20, 14.25 and PostgreSQL 19 RC 2. The update fixes 52 security vulnerabilities plus more than 140 bugs from recent months. PostgreSQL 14 is end-of-life, so no later security or bug fixes will ship, and flaws found afterward stay open. The group suggests anyone running 14 in production plan an upgrade to a supported version. Some issues may require extra steps after updating; those steps sit in the release notes.
Closed flaws include six CVSS v3.1 8.8 bugs that execute arbitrary code: CVE-2026-6460 (type confusion following ALTER ... SET DATA TYPE), CVE-2026-18447 (output-parameter types), CVE-2026-116304 (parallel RECORD typmod use-after-free), CVE-2026-116306 (composite type changed while a field is assigned), CVE-2026-116307 (plperl prepared-query use-after-free) and CVE-2026-116309 (plperl blessed-reference confusion that may execute arbitrary code). Also closed were CVE-2026-14661 (8.1, file appends via dblink or subscriptions), CVE-2026-6467 (7.2, arbitrary SQL from a mishandled extension-script schema), CVE-2026-16237 (5.4, INSERT ... ON CONFLICT still reading or changing rows despite a WHERE on an auto-updatable view), CVE-2026-116311 (5.4, DROP OWNED stripping other tables' restrictive row-security policies), CVE-2026-116308 (4.3, dict_int past empty tokens), CVE-2026-116310 (4.3, freed storage in COPY errors), CVE-2026-16240 (3.7, manifest text used as a format string by pg_basebackup) and CVE-2026-116303 (3.1, cast EXECUTE privilege skipped by foreign-key and JSON conversions).
Leaving version 14
Umair Shahid wrote on 11 November 2026 that each major version has five years of support: 15 until 11 November 2027, 16 until 9 November 2028, 17 until 8 November 2029 and 18 until 14 November 2030. He said a move to 18 buys four years, versus one or two for 15 or 16. pg_upgrade --link took under 10 minutes on one customer's 100 GB production database. For a cluster that qualifies, he uses blue-green, with a write pause of seconds.