Plan this weekVulnerabilities

PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security flaws, and PostgreSQL 14 reaches end of life: update your databases

On 12 November 2026 the PostgreSQL project released updates for versions 18 to 14 that fix 52 security vulnerabilities, 35 of them rated 8.0 or higher. Several can lead to arbitrary code execution. The announcement does not report any exploitation. Version 14 gets its last release, so it will no longer receive security fixes. What to check and what to do.

How urgent

Plan this week

Who is affected

PostgreSQL 18, 17, 16, 15 and 14 before the 12 November 2026 releases (fixed in 18.7, 17.12, 16.16, 15.20 and 14.25); PostgreSQL 14 is now end of life and gets no more fixes

What to do

Check your PostgreSQL version; update to the latest minor release of your major version (no dump and reload needed); if you run PostgreSQL 14, plan an upgrade to a supported version; then follow the reindex and backup steps in the announcement that apply to you

Published 15 Nov 2026 · Sources last checked 15 Nov 2026No. 87 / 87

What happened

On 12 November 2026 the PostgreSQL project released 18.7, 17.12, 16.16, 15.20 and 14.25, together with the second release candidate of PostgreSQL 19. The announcement says the update fixes 52 security vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary, and the list in the announcement has 52 entries. It also says 14.25 is the final release of PostgreSQL 14, which is now end of life and will no longer receive security and bug fixes.

What the sources say about severity and exposure

  • Scores: the announcement gives CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary v3.1 scores from 3.1 to 8.8. Counting its list, 35 of the 52 are rated 8.0 or higher.
  • Code execution: several entries are described as allowing arbitrary code execution, all rated 8.8. Examples are CVE-2026-6460 (a type confusion after ALTER ... SET DATA TYPE), CVE-2026-18447 (a type confusion with output parameters), CVE-2026-120147 (a use-after-free in dblink), and CVE-2026-120145 (a logical replication subscriber that can write to system catalogs). Some of the others are in client tools: pg_restore (CVE-2026-116314) and pg_dump with a tar restore (CVE-2026-116330). Several of these need user interaction, such as restoring a file someone gave you.
  • Affected versions: the security page lists the entries we checked as affecting versions 18 through 14, fixed in the five new releases. One entry, in vacuumdb (CVE-2026-116313, 7.2), affects version 18 only.
  • Exploitation: the announcement says nothing about attacks in the wild, and it does not name who reported the flaws.
  • Upgrade steps: a minor update needs no dump and reload and no pg_upgrade: stop PostgreSQL and replace the binaries. The announcement lists a few follow-up steps that apply only in some cases (see below).

How serious it is

This is a large security batch for a very widely used open source database. Several flaws need the attacker to already have some access (a database account, or a file you restore), so this is not the same as an internet-wide remote flaw, and nobody has reported attacks. It is still worth updating this week, because the fixes are public and many are in the core server. The most urgent group is anyone running PostgreSQL 14: with no more security fixes, every new flaw stays open.

What to do

  1. Find your version: run SELECT version(); in psql, or postgres --version on the server.
  2. Update to the newest minor release of your major version (18.7, 17.12, 16.16 or 15.20), or to your distribution's or cloud provider's fixed package. A managed service (RDS, Cloud SQL, and similar) usually applies it for you: check that its maintenance window has run.
  3. If you run PostgreSQL 14, plan the move to a supported major version now. Update to 14.25 in the meantime, but it is the last one.
  4. Follow the announcement's reindex steps that apply to you: GIN indexes affected by the corruption fixes, GiST indexes using gist_trgm_ops (the pg_trgm extension), B-tree indexes on bpchar columns declared without a length, and REINDEX TABLE if you see "missing chunk number" errors.
  5. If you use incremental backupsBackup A copy of your data kept apart from the original, so you can recover it if something is lost, broken or locked. Tap again to open the glossary, take a new full backup after updating and use it as the base for the next incrementals.
  6. If you use partitioned tables, run the announcement's query to look for NOT NULL NO INHERIT constraints and fix them as it describes.
  7. Until you can update, restore dumps only from sources you trust, because several client-tool flaws need you to open a crafted file.

Steps 1, 3 and 7 are ours; the rest follow the announcement.

What we could not confirm

Some social media posts about this release call one of the bugs "22 years old". The announcement does not say that, so we do not repeat it. The announcement does not list affected versions for each CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary; we read them from the security page for the entries we checked and could not verify all 52. We did not read The Hacker News's report, and we did not test any of the flaws ourselves.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks