CVE-2026-2360: Improper search_path protection in PostgreSQL Anonymizer 2.5 allows any user to gain superuser privileges in PostgreSQL 14
PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a custom operator in the public schema and place malicious code in that operator. This operator will later be executed with superuser privileges when the extension is created. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved if a superuser adds a new schema in her/his own searchpath and grants the CREATE privilege on that schema to untrusted users, both actions being clearly discouraged by the PostgreSQL documentation. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-2360?
CVE-2026-2360 is classified as a critical vulnerability due to the risk of unauthorized superuser access in PostgreSQL.
How do I fix CVE-2026-2360?
To fix CVE-2026-2360, ensure that the search_path is properly secured and upgrade to a version of PostgreSQL Anonymizer higher than 3.0.1.
Who is affected by CVE-2026-2360?
CVE-2026-2360 affects users of PostgreSQL Anonymizer prior to version 3.0.1 and PostgreSQL version 14.
What can attackers do using CVE-2026-2360?
Attackers can gain superuser privileges by creating a malicious custom operator in the public schema.
How can I verify if my system is vulnerable to CVE-2026-2360?
You can verify vulnerability to CVE-2026-2360 by checking for vulnerable versions of PostgreSQL Anonymizer and reviewing the configuration of the search_path.