The PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25 on November 12, together with the second release candidate of 19, fixing 52 security vulnerabilities and over 140 other bugs. 32 of the 52 carry a CVSS score of 8.8, mostly of the "executes arbitrary code" kind. 14.25 is the final release of PostgreSQL 14, which will receive no more security fixes. A minor update needs neither a dump and reload nor pg_upgrade: stop the server, install the new binaries and start it again. This time, though, several situations call for extra steps after the update, described below.
Most of them require a database login
- Going by the score vectors on the official security page, 44 of the 52 require the attacker to log in to the database with an ordinary account, and 3 require a highly privileged account. What a logged-in attacker can do is serious; CVE-2026-6460 (8.8), for example, is a type confusion that executes arbitrary code. Databases shared by several users, or where you have given accounts to customers, matter most.
- 3 require you to restore or connect to something the attacker prepared: restoring an untrusted dump with pg_restore or psql (CVE-2026-116314, CVE-2026-116330), and a logical replication subscriber having its system catalogs written by a malicious publisher (CVE-2026-120145). Until you have updated, do not restore dumps someone else gave you.
- Only 2 can be triggered without logging in, and both score low: a spinlock leak caused by cancel requests in version 18 (CVE-2026-116322, 5.3) and a format string issue in pg_basebackup (CVE-2026-16240, 3.7). The database port 5432 should not be open to the internet in the first place; let only your application servers connect, as covered in ufw firewall and SSH key login.
Where the distributions stand
- Debian: DSA-6625-1 on November 13 fixed postgresql-17 in Debian 13 (
17.12-0+deb13u1), and DLA-4905-1 on November 14 fixed postgresql-15 in Debian 12 (15.20-0+deb12u1). - Ubuntu: as of November 13, Ubuntu's vulnerability pages still showed "needs-triage" for postgresql-14 on 22.04, postgresql-16 on 24.04 and postgresql-18 on 26.04, with no fixed packages yet.
- The official PostgreSQL apt repository (apt.postgresql.org) already has the new versions; on 22.04, for example, postgresql-16 is
16.16-1.pgdg22.04+1and postgresql-14 is14.25-1.pgdg22.04+1. If you installed from it,sudo apt update && sudo apt upgradeis enough; if you run PostgreSQL in Docker, pull the new image and recreate the container, as covered in our Docker primer. - PostgreSQL 14 is the default on 22.04. Upstream no longer supports it, so plan a major version upgrade (pg_upgrade, or dump and restore), and take a backup before you start, as covered in VPS backup strategies.
What to do after updating
- If you suspect a GIN index is affected by the corruption issues fixed in this release, rebuild it:
REINDEX INDEX your_index_name; - If you use the pg_trgm extension, rebuild every GiST index that uses
gist_trgm_ops. - If reading a table gives missing chunk number errors, rebuild the whole table, which also rebuilds its TOAST table:
REINDEX TABLE your_table_name; - If you use incremental backups, take a new full backup after updating and base later incremental backups on it.
- If you have partitioned tables, the query below finds NOT NULL NO INHERIT constraints on them: drop the ones you do not need, and repair the ones you keep with ALTER TABLE ... ALTER CONSTRAINT ... INHERIT (the repair fails if a partition already has NULL values in that column).
SELECT conrelid::regclass, conname FROM pg_constraint WHERE contype = 'n' AND connoinherit AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');
B-tree indexes on bpchar columns declared without a length also need rebuilding after the update; columns declared as char(n) are not affected. If you skipped one or more earlier minor releases, also follow the post-update steps in their release notes. PostgreSQL 19 is planned for general availability on November 19.