Post

Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)

A researcher explains how changing a composite type after preparing a query could make PostgreSQL interpret an old value using a new field layout, leading to memory corruption and code execution.

The demonstrated crash starts with a UUID field changed to bytea; the cached value is then interpreted as a bytea header and pointer. The author says an ordinary login role can trigger the flaw, which matters especially for managed PostgreSQL’s tenant isolation. CVE-2026-6460 covers the type-confusion fix.