Linux

PostgreSQL 18.7 and Friends Fix 52 CVEs; PostgreSQL 14 Is EOL

PostgreSQL minor releases fix 52 vulnerabilities and 140+ bugs, end PostgreSQL 14 support, and set PostgreSQL 19 for November 19.

13 November 2026  ·  5 min read  ·  Anand

PostgreSQL 18.7 and Friends Fix 52 CVEs; PostgreSQL 14 Is EOL

The PostgreSQL Global Development Group released PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 on November 12, 2026, along with a second release candidate for PostgreSQL 19. This is a bigger minor update than usual. It fixes 52 security vulnerabilities and more than 140 bugs. It is also the last release PostgreSQL 14 will ever get. If you run PostgreSQL behind a web application, a SaaS product or an internal tool, put this update on your schedule this week, and if you are still on 14, start planning a major upgrade.

What this release fixes

The security fixes are the headline. The highest CVSS score in the batch is 8.8, and roughly 32 of the 52 issues carry that score. Many are memory-safety bugs (use-after-free, buffer overflows and type confusion) that an authenticated database user could use to run arbitrary code on the server. Some examples:

  • CVE-2026-6460: type confusion after ALTER ... SET DATA TYPE that can lead to code execution.
  • CVE-2026-116314 and CVE-2026-116330: pg_restore and pg_dump tar archive issues that can run code or psql commands when you restore a malicious dump.
  • CVE-2026-120145: logical replication writing to subscriber system catalogs.
  • Several issues in plperl, pltcl and dblink, plus SQL injection bugs in reindexdb (CVE-2026-116325) and extension scripts (CVE-2026-120153).
  • Row security and view bypasses involving INSERT ... ON CONFLICT and DROP OWNED.

The restore-related CVEs are worth noting for agencies and hosting providers. If you ever restore dumps that come from customers or other third parties, those dumps are attacker-controlled input until your tools are patched.

The bug fixes matter just as much for data integrity. The release fixes GIN index corruption that could make queries miss rows or return the wrong ones, possible corruption in pg_trgm GiST indexes, missed updates after REINDEX CONCURRENTLY on TOAST tables, and several problems that could produce corrupt incremental backups. There are also planner fixes for wrong results with LATERAL, outer joins and partition pruning. Time zone data moves to tzdata 2026f.

How to apply the update

A minor release does not need a dump and reload or pg_upgrade. You stop the server, replace the binaries and start it again. With your distribution or the PGDG packages, that usually means:

# Debian / Ubuntu (PGDG apt repository, example for version 17)
sudo apt update
sudo apt install --only-upgrade postgresql-17 postgresql-client-17

# RHEL / Rocky / AlmaLinux (PGDG dnf repository, example for version 17)
sudo dnf upgrade 'postgresql17*'
sudo systemctl restart postgresql-17

# Confirm the running version
psql -c 'SELECT version();'

Check the running server, not just the package version. A package can be upgraded while the old binary keeps running until someone restarts it. On replicated setups, update the standbys first and then the primary, so you have only one short failover or restart window.

Post-update checklist

Some fixes stop new damage but do not repair what is already there. After upgrading, go through this list:

  1. GIN indexes: if you suspect wrong results, rebuild them with REINDEX INDEX name;
  2. pg_trgm: reindex GiST indexes that use the gist_trgm_ops operator class.
  3. missing chunk number errors: run REINDEX TABLE name;, which also rebuilds the TOAST table index.
  4. Incremental backups: take a fresh full backup after the update and use it as the new base.
  5. bpchar columns: reindex B-tree indexes on columns declared as bpchar without a length. Columns declared as char(n) are not affected.
  6. Partitioned tables: look for NOT NULL NO INHERIT constraints, which are no longer allowed:
SELECT conrelid::regclass, conname
FROM pg_constraint
WHERE contype = 'n' AND connoinherit
  AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');

Drop any constraint you do not need, or fix it with ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. That command fails if a partition has NULLs in the column, so clean the data first. If you skipped earlier minor releases, also read their release notes for extra steps.

PostgreSQL 14 is now end of life

14.25 is the final PostgreSQL 14 release. From now on it gets no security or bug fixes, so any vulnerability found after this point stays open. Moving to a supported major version means using pg_upgrade or a dump and restore. Test it on a copy first, and check your extensions, connection poolers and application drivers.

Branch Latest Status
18 18.7 Supported
17 17.12 Supported
16 16.16 Supported
15 15.20 Supported
14 14.25 End of life

PostgreSQL 19 is days away

PostgreSQL 19 RC 2 is out, and general availability is planned for November 19, 2026. If you are already testing 19, two points from the notes matter. If you use pg_upgrade and have indexes on full text search, pg_trgm or fuzzystrmatch, read the Migration to Version 19 section, because you may need to reindex. And if you upgraded from RC 1, drop or redefine objects that use JSON_ARRAY() or JSON_OBJECT() over arrays, composite or range types in expression indexes, generated columns or partition keys. That change was reverted, and dump, restore and pg_upgrade will fail on those objects. For teams leaving 14, it may be worth waiting a minor release or two on 19 and moving to 18 now.

How TechProvidence can help

We patch and upgrade PostgreSQL for clients on Debian, Ubuntu, RHEL-family and AWS RDS, including replicated clusters where downtime has to stay short. If you need this minor update rolled out, the post-update checks done, or a PostgreSQL 14 server moved to a supported version with a tested rollback plan, contact us.

Source: PostgreSQL Global Development Group

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.