Subscribe
0%
Illustration for: PostgreSQL 18.7 fixes 52 CVEs, including a 22-year-old bug that lets ordinary users run code. What to do

PostgreSQL 18.7 fixes 52 CVEs, including a 22-year-old bug that lets ordinary users run code. What to do

The November 12 PostgreSQL releases (18.7, 17.12, 16.16, 15.20, 14.25) patch 52 security flaws, 32 of them rated 8.8. Most let a logged-in user with modest rights run code on the server. Nobody has reported attacks yet, but a researcher has published crash code for one of them, and PostgreSQL 14 now gets no more fixes.

Listen to this article0:00 / 6:50

The PostgreSQL project shipped 18.7, 17.12, 16.16, 15.20 and 14.25 on November 12. According to the project's security page, the releases fix 52 CVEs: 43 in the core server, 6 in client tools such as pg_dump, pg_restore and psql, and 3 in contrib modules. The same releases fix more than 140 ordinary bugs, several of which can quietly corrupt indexes or backups.

None of the 52 is rated critical, but 38 are rated high. Most of those follow the same pattern: someone who can already log in and create objects, a common setup for app accounts and analytics users, can make the server run their own code as the PostgreSQL operating-system user.

The numbers

Count
Total CVEs 52
High (7.0–8.9) 38, of which 32 are rated 8.8
Medium (4.0–6.9) 12
Low 2
Critical 0
Affect every supported branch (14–18) Most; a few hit only 18 or 17–18

Source: PostgreSQL security page. Counts by TechMeasured from the project's list.

The 22-year-old bug

The headline flaw is CVE-2026-6460 (CVSS 8.8), a type confusion that shows up after a column's type is changed with ALTER ... SET DATA TYPE. The Hacker News traces its root to a May 2004 change that first let PostgreSQL alter column types. When a composite type changes, older values can linger elsewhere in the server and be read as if they had the new layout. The fix adds version checks to catch those mismatches.

Researcher Mehmet Ince, credited on CVE-2026-6460 and five other flaws, has published a write-up. According to The Hacker News, it shows SQL that crashes an unpatched 18.6 server and a memory-leak step, but leaves out the final code-execution query. He says he could trigger the crash as a low-privileged login role. More than a dozen reporters are credited on that CVE overall.

Many of the other high-rated bugs are similar memory-safety problems in less obvious places. They include PL/pgSQL record fields, foreign-data-wrapper batch inserts, dblink, logical replication, text-search functions (ts_rank_cd, tsvector_delete), and five separate bugs in PL/Perl.

Bugs that hit your laptop, not the server

Six CVEs are in client tools, and patching the server doesn't fix them:

  • pg_restore can run attacker code when it reads a crafted non-plain archive (CVE-2026-116314, 8.8).
  • pg_dump tar archives don't stop a malicious restore.sql from injecting psql commands (CVE-2026-116330, 8.8).
  • pg_dump (18 only) and reindexdb (17–18) have SQL-injection bugs through crafted object names (CVE-2026-116318, CVE-2026-116325).
  • vacuumdb --missing-stats-only (18) lets a database owner run code as whoever runs vacuumdb (CVE-2026-116313).

The one that needs no login

CVE-2026-116322 (CVSS 5.3, PostgreSQL 18 only) is a spinlock leak triggered by a cancel request sent before authentication. The Hacker News describes it as the only flaw in the batch that needs neither a login nor user interaction, and says an unauthenticated client can use it to force PostgreSQL 18 servers to restart.

Is anyone exploiting it?

Not that anyone has reported. The Hacker News says the project hasn't reported any attacks, and CISA's CVE record lists exploitation as "none." Public crash code for CVE-2026-6460 shortens the road for attackers, so don't wait.

What to do

  1. Update the server. Install 18.7, 17.12, 16.16, 15.20 or 14.25. These are minor releases, so you stop the server and swap binaries, with no dump/reload or pg_upgrade.
  2. Update client tools everywhere. Upgrade psql, pg_dump, pg_restore, reindexdb and vacuumdb on laptops, CI runners and backup hosts, not just on the database box. Until then, don't restore archives you didn't make.
  3. Review who can create objects. The worst bugs need an account that can create tables, types or functions. Tighten CREATE rights for app and reporting roles, and treat untrusted PL/Perl or PL/Tcl code as a risk.
  4. Do the post-update chores the release notes call for:
    • Reindex GIN indexes you suspect are corrupted.
    • Reindex every pg_trgm GiST index using gist_trgm_ops.
    • Reindex B-tree indexes on length-less bpchar columns.
    • If you see missing chunk number errors, run REINDEX TABLE on the affected tables.
    • Take a new full backup if you use incremental backups.
  5. Leave PostgreSQL 14. The project says 14.25 is its final release, so future fixes won't reach it. PostgreSQL 19 is scheduled for general availability on November 19.
  6. On a managed service? Ince says he worked with providers including AWS, Azure, Google AlloyDB, Supabase, Databricks and Ubicloud, but The Hacker News doesn't give their patch status. Check your provider's maintenance notices for the 18.7-level builds.

Who should care most

Anyone running multi-tenant PostgreSQL, or giving customers or analysts their own SQL accounts: hosting platforms, SaaS products with per-customer schemas, and BI setups. In those setups, "authenticated user" can mean a stranger.

Sources

  1. PostgreSQL Global Development Group — PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2 released (announcement text) postgresql.org
  2. PostgreSQL — Security Information postgresql.org
  3. The Hacker News — PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE thehackernews.com

#PostgreSQL#CVE-2026-6460#CVE-2026-116322#database#patch now#pg_dump#end of life