CVE-2026-6470: PostgreSQL fails to check type USAGE privilege
Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 18.5 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 17.11 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 16.15 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 15.19 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 14.24
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6470?
The severity of CVE-2026-6470 is medium with a CVSS score of 4.3.
How does CVE-2026-6470 affect PostgreSQL users?
CVE-2026-6470 allows a user with object creation privileges to create a dependency that can deny service during DDL operations.
What causes the vulnerability in CVE-2026-6470?
The vulnerability in CVE-2026-6470 is caused by missing authorization checks in PostgreSQL when executing certain DDL commands.
How can I mitigate CVE-2026-6470?
To mitigate CVE-2026-6470, ensure that proper user privileges are set and review DDL operations involving type dependencies.
Is there a patch available for CVE-2026-6470?
Yes, updates for PostgreSQL that address CVE-2026-6470 are available in the latest releases.