22-year-old PostgreSQL bug enables remote code execution
Archived — this story has rotated out of today’s deck. It is kept here in full.
The gist
Vulnerability researcher Mehmet Ince published how a 2004 PostgreSQL type-confusion flaw yields remote code execution (CVE-2026-6460).
The fix shipped in a November update covering 52 vulnerabilities, so admins should patch.
Background
Mehmet Ince is a vulnerability researcher who writes a blog series on PostgreSQL security. PostgreSQL is a widely used open-source database, and its Global Development Group maintains it. Ince began in mid-2026 exploiting memory-corruption bugs in PostgreSQL extensions such as pg_clickhouse, which led him to ask how PostgreSQL itself decides what a value is. The underlying mutable-row-type primitive dates to a 2004 commit, while the exploitation technique relies on expanded-object support added in 2015.
How it unfolded
- May 5, 2004Commit 077db40fa1f3 introduced the mutable-row-type primitive via ALTER TABLE ... ALTER COLUMN ... TYPE, making the flaw roughly 22 years old.
- May 14, 2015Commit 1dc5ebc9077a added expanded-object support, which the exploitation technique relies on.
- Jun 23, 2026The pg_clickhouse out-of-bounds write and read chain was fixed by the vendor after the researcher reported it.
- Nov 9, 2026Ince published Part 3/6 of his blog series describing turning the type-confusion primitive into RCE (CVE-2026-6460).
- Nov 12, 2026The PostgreSQL Global Development Group released versions 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 security vulnerabilities and more than 140 other bugs.
- Nov 13, 2026Help Net Security reported the November 2026 update also ends support for PostgreSQL 14.
Key terms
- remote code execution
- A security flaw letting an attacker run any commands or code of their choice on a target machine or process.
- CVE-2026-6460
- A unique identifier in the CVE system for a publicly known information-security vulnerability.
Source: Wikipedia
Who’s saying what
- Expert
- Ince said he gave PostgreSQL a value inside a composite type, changed the type of one of its fields and read the value back, and that the resulting type confusion led to one of the most reliable memory-corruption exploits he has seen; he said he reported 21 cases in total.
- Public
- Community discussion debated whether this really counts as 'RCE' versus privilege escalation requiring prior database access, while others dug into the PostgreSQL internals that made the bug possible.
- Support
- Hacker News commenter igbanam thanked the author for sharing his path to the zero-day, saying the context and story help.
Still unverified
Community discussion debated whether the issue really counts as 'RCE' versus privilege escalation requiring prior database access.