The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-6460: PostgreSQL Fixes 22-Year-Old RCE Flaw

By The Daily Byte ·15 Nov 2026 ·3 min read
Server racks in a data centre corridor, illustrating the database servers affected by the PostgreSQL security update

The PostgreSQL project has released security updates fixing 52 vulnerabilities across all supported versions of the open-source database, including a high-severity flaw that lets a database user who can create objects run code on the server. The flaw, tracked as CVE-2026-6460, has a CVSS score of 8.8 and traces its roots to a change made in 2004.

The updates, released on 12 November 2026, cover PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25, along with a second release candidate of PostgreSQL 19. The release also contains more than 140 bug fixes. Version 14.25 is the final release of the PostgreSQL 14 branch, which has now reached end of life.

How the flaw works

CVE-2026-6460 is a type confusion flaw in how PostgreSQL handles composite types, which are data types built from named fields, each with its own data type. A field's type can be changed while older values of that type are still held in other parts of the server, so the server can then read an old value as if it were the new type. An authenticated database user with permission to create or alter database objects can exploit that confusion to execute arbitrary code with the rights of the operating system user that runs PostgreSQL.

Security researcher Mehmet Ince, who reported the flaw, described a working exploit demonstrated on PostgreSQL 18.6. He traced the root of the bug to 5 May 2004, when PostgreSQL gained the ability to change a column's type, making this one of the longest-lived code execution flaws the project has disclosed. Ince published the crash and address-leak steps in full but deliberately did not publish the final step that makes the server run a command. The PostgreSQL project has not reported any attacks using the flaw, and the CISA assessment in the CVE record lists exploitation as none.

One of 52 fixes in the release

The project rates 32 of the 52 flaws fixed in this release at 8.8, the highest score in the batch. Only one flaw in the server requires neither a login nor any user action: CVE-2026-116322, which lets an unauthenticated client trigger a restart of PostgreSQL 18 servers. Several other fixes are in client tools, including flaws where a crafted archive can make pg_restore run code as the user running it, and where a compromised source server can make psql run code through the restore script in pg_dump's tar output.

Administrators should update to 18.7, 17.12, 16.16, 15.20 or 14.25, matching their major version. The fix is a minor-release update that needs no dump, reload or pg_upgrade for a same-major upgrade. Full protection from CVE-2026-6460 also requires rebuilding any C-language extensions installed on the server, since extensions built against older releases still load but may not be fully protected. Teams on managed PostgreSQL should confirm with their provider that the fix has been applied, and should review which accounts hold object-creation rights, revoking CREATE on schemas from roles that do not need it.

Sources: The Hacker News; PostgreSQL Global Development Group release announcement of 12 November 2026.