Project Subscriptions
No data.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Remove the k_anonymity feature with 'DROP FUNCTION anon.k_anonymity();'. This is a user-facing function with no internal dependencies.
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/640 |
|
Wed, 27 May 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 27 May 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a table and placing malicious code inside a column identifier. If a superuser calls the k-anonymity function, the malicious code is executed with superuser privileges. 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 by a user who was explicitly granted the CREATE TABLE privilege. The problem is resolved in PostgreSQL Anonymizer 3.1.0 and further versions | |
| Title | PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-05-27T15:27:45.957Z
Reserved: 2026-05-26T16:36:40.963Z
Link: CVE-2026-9617
Updated: 2026-05-27T15:14:00.451Z
Status : Awaiting Analysis
Published: 2026-05-27T14:17:40.273
Modified: 2026-05-27T14:54:20.160
Link: CVE-2026-9617
No data.
OpenCVE Enrichment
Updated: 2026-05-27T21:30:34Z