thethreatdeskFiled from the front lines of cybersecurity
VulnerabilitiesHigh

PostgreSQL fixes 52 security flaws, including a 22-year-old code execution bug

New PostgreSQL releases fix 52 flaws, led by a type confusion bug that can let a database user run code on the server. Version 14 has now reached end of life.

The PostgreSQL project shipped updates on Nov 12 that fix 52 security vulnerabilities. The fixed releases are 18.7, 17.12, 16.16, 15.20 and 14.25.

The headline bug

The most notable flaw, CVE-2026-6460, is a type confusion bug in composite types rated 8.8. A database user who can create objects may be able to run code on the server as the operating system account that runs PostgreSQL. Its roots trace back to a 2004 change that allowed a column's type to be altered, which is why it is being described as a 22-year-old bug.

Researcher Mehmet Ince published a crash and memory-leak exploit against version 18.6 but held back the final code execution step. He also shared proofs of concept privately with managed database providers.

Other fixes

No attacks have been reported. PostgreSQL 14.25 is the final release for version 14, so anyone still on 14 should plan an upgrade.

Who's affected

Anyone running self-managed PostgreSQL servers, plus admins who use pg_dump, pg_restore and psql against databases they don't fully control.

What to do

Update to 18.7, 17.12, 16.16, 15.20 or 14.25, rebuild C-language extensions at the same time, and restart the server. Update client tools on every machine, follow the reindexing steps in the release notes, and plan a move off PostgreSQL 14.

Tracked flaws:CVE-2026-6460CVE-2026-116322