Home

Description

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 search_path 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

PUBLISHED Reserved 2026-02-11 | Published 2026-02-11 | Updated 2026-02-11 | Assigner PostgreSQL




HIGH: 8.0CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Problem types

Uncontrolled Search Path Element

Product status

Default status
unaffected

1 (rpm) before 3.0.1
affected

Credits

The PostgreSQL Anonymizer project thanks Daniel Bakker for reporting this problem.

References

gitlab.com/...bo/postgresql_anonymizer/-/blob/latest/NEWS.md

gitlab.com/dalibo/postgresql_anonymizer/-/issues/616

www.postgresql.org/docs/current/ddl-schemas.html

cve.org (CVE-2026-2360)

nvd.nist.gov (CVE-2026-2360)

Download JSON