CVE-2026-6460 is a type-confusion vulnerability in PostgreSQL’s core server that can let a database object creator execute arbitrary code with the operating-system privileges of the database process. The main attack route involves changing a column’s type with ALTER ... SET DATA TYPE, though other DDL sequences can also trigger the flaw, including adding a column, rolling back, and adding a column again. The underlying weakness is that PostgreSQL did not adequately track typed values, and those values did not identify their own types. As a result, stale values could be reused in data dictionary entries, PL/pgSQL variables, and other parts of the system.
Successful exploitation can compromise the confidentiality, integrity, and availability of the database host, rather than being limited to manipulating database records. The vulnerability has a CVSS 3.0 score of 8.8, with network access and low privileges required; it does not require user interaction. Affected releases are PostgreSQL 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20, and 14 before 14.25. Fixes for all listed branches were published on November 12, 2026. Administrators using an affected release should upgrade to the corresponding fixed version.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.