CVE-2026-6472: PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege
Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use searchpath to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
Other sources
PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 18.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.10 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.18 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.23
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6472?
CVE-2026-6472 is classified as a high-severity vulnerability due to the potential for unauthorized data access.
How do I fix CVE-2026-6472?
To fix CVE-2026-6472, ensure that you are using an updated version of PostgreSQL that addresses this vulnerability.
What systems are affected by CVE-2026-6472?
CVE-2026-6472 affects multiple versions of PostgreSQL, specifically versions up to 18.4, 17.10, 16.14, 15.18, and 14.23.
What are the implications of CVE-2026-6472?
The implications of CVE-2026-6472 include the risk of query hijacking and unauthorized manipulation of user-defined types.
Can CVE-2026-6472 affect data integrity?
Yes, CVE-2026-6472 can compromise data integrity by allowing unauthorized queries to execute within the affected PostgreSQL environments.