PostgreSQL
PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 18, < 18.7
- >= 17, < 17.12
- >= 16, < 16.16
- >= 15, < 15.20
- < 14.25
Fixed in 18.7, 17.12, 16.16, 15.20, 14.25
Mitigation
Upgrade PostgreSQL to 18.7 or 17.12 or 16.16 or 15.20 or 14.25 or later.
Timeline
Days relative to CVE publicationFirst public PoC 17 h after publication; not in CISA KEV. First PoC: slabbdev/postgresql-type-confusion-cve-2026-6460 (created 13 Nov 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| slabbdev/postgresql-type-confusion-cve-2026-6460 | 13 Nov 2026 +17 h | 14 Nov 2026 | 0 | PoC |
| chor4o/CVE-2026-6460-POC | 13 Nov 2026 +1.2 d | 14 Nov 2026 | 1 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.