PostgreSQL 18.7 fixes 52 flaws; PostgreSQL 14 hits end of life
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security flaws, including CVE-2026-6460 code execution. PostgreSQL 14 gets no more fixes. Patch now.
PostgreSQL shipped a heavy security update on November 12. Versions 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security vulnerabilities and more than 140 bugs, per the release announcement. One of them lets a database user run code on the server. And PostgreSQL 14 just got its last release. If your app runs on Postgres, this is this week's work.
What actually happened
The headline flaw is CVE-2026-6460, CVSS 8.8. It is a type confusion in the core server. A user who can create objects can use ALTER ... SET DATA TYPE to execute arbitrary code as the operating system user that runs the database. Every version before the new releases is affected.
The Hacker News reports that the researcher traces the root of the bug to 2004, and that a technical writeup with a working exploit path for 18.6 is public. The project has reported no attacks.
Other fixes at the same level:
- CVE-2026-116314 (8.8):
pg_restorecan execute arbitrary code from a crafted archive. - CVE-2026-116330 (8.8): a
pg_dumptar archive can injectpsqlcommands on restore. - CVE-2026-120145 (8.8): logical replication can write to system catalogs on the subscriber.
- CVE-2026-14661 (8.1):
dblinkand subscriptions can append to arbitrary files.
The update itself is small: stop the server, swap the binaries, start. No dump and reload. The same announcement puts PostgreSQL 19 general availability on November 19.
Why the PostgreSQL update matters for your business
"Authenticated" is a low bar. Your app connects with a database role. If that role can create tables, an SQL injection in your app is now a route to the server's operating system. Patch, then remove CREATE rights from the role your app uses at runtime. Migrations can use a different role.
PostgreSQL 14 is finished. 14.25 is the final release. The next flaw of this kind will not get a fix. If you are on 14, schedule the major upgrade now, not after the next advisory.
Treat dump files as code. Two of the fixes concern restore. Do not restore an archive from a vendor, a client or an old contractor on a machine that matters until you are on the fixed client tools.
Read the post-update steps. The announcement lists reindex work for specific cases: GiST indexes that use gist_trgm_ops, B-tree indexes on bpchar columns declared without a length, and GIN indexes if you suspect corruption. If you use incremental backups, take a new full backup after the update.
Managed is not automatic. On RDS, Cloud SQL, Supabase or Neon, the provider ships the minor version. You often still pick the maintenance window. Check which version you run today: SELECT version();
Key takeaways
- PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security flaws and 140+ bugs
- CVE-2026-6460 (CVSS 8.8) lets a user who can create objects run code as the database OS user
- PostgreSQL 14 is end of life; 14.25 is its final release
- No dump and reload needed, but some indexes need a reindex
- Remove CREATE rights from the role your app uses at runtime
Still on PostgreSQL 14, or not sure? We plan and run Postgres upgrades with a tested rollback, and we cut app roles down to what they need. Tell us your version, or see what we build.
Sources: PostgreSQL release announcement, PostgreSQL CVE-2026-6460, The Hacker News.
- #postgresql
- #security
- #database
- #patching
- #cve
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
TSMC employee data breach traced to a cloud provider
TSMC confirmed an employee data breach in an SEC filing. The leaked data matches records at a cloud service provider. Inventory the HR data your vendors hold.
Read itSignDrop Windows zero-day: SYSTEM access, no patch, no CVE
The SignDrop Windows zero-day uses CLFS and Defender to give a standard user SYSTEM rights. No patch or CVE exists. Keep CLFS authentication on and cut admin rights.
Read it