CVE-2026-9617

published 27 May 2026 · updated 28 May 2026

PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function

6.8MediumCVSS 6.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.1.0.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
DALIBO>=1 <3.1.03.1.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-9617 severity on Zeptric[![CVE-2026-9617](https://zeptric.io/badge/cve/CVE-2026-9617.svg)](https://zeptric.io/cve/CVE-2026-9617)