PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 14.25, 15.20, 16.16 and 2 more.
Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily. Other DDL attack routes exist, such as "ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN". The system had inadequate tracking of typed values, and values were not self-identifying. Stale values could appear in data dictionary entries, PL/pgSQL variables, and many other parts of the system. PostgreSQL Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| <14.25, >=15 <15.20, >=16 <16.16, >=17 <17.12, >=18 <18.7 | 14.25, 15.20, 16.16, 17.12, 18.7 |
Exploit evidence
2 public sources
Coverage
News and research mentioning this CVE
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket