CVE-2026-2361
Privilege Escalation via Malicious View in PostgreSQL Anonymizer
Publication date: 2026-02-11
Last updated on: 2026-02-12
Assigner: PostgreSQL
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dalibo | postgresql_anonymizer | 3.0.1 |
| dalibo | postgresql_anonymizer | From 14.0 (inc) to 15.0 (inc) |
| postgresql_anonymizer | 3.0.1 | * |
| postgresql | 15 | * |
| postgresql | 14 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-427 | The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
PostgreSQL Anonymizer has a vulnerability that allows a user with CREATE privileges to gain superuser privileges by creating a temporary view based on a function containing malicious code. When the function anon.get_tablesample_ratio is called, the malicious code executes with superuser privileges, effectively elevating the user's privileges.
This issue affects PostgreSQL 15 and later, with a higher risk in PostgreSQL 14 or instances upgraded from version 14 or earlier because the public schema creation permission is granted by default in those versions.
The vulnerability is fixed in PostgreSQL Anonymizer version 3.0.1 and later.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with CREATE privileges to escalate their privileges to superuser level within the PostgreSQL database.
With superuser privileges, the attacker can execute arbitrary code with the highest level of access, potentially compromising the entire database system.
This can lead to unauthorized data access, data modification, or disruption of database operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade PostgreSQL Anonymizer to version 3.0.1 or later where the issue is resolved.
Additionally, be cautious with users having CREATE privileges, especially in PostgreSQL 15 and later, and review permissions on the public schema in PostgreSQL 14 or instances upgraded from earlier versions, as creation permission is granted by default there.