CVE-2026-9617 PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function
A malicious column name in PostgreSQL Anonymizer allows SQL injection, enabling privilege escalation to superuser when the k-anonymity function is executed.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-9617?
CVE-2026-9617 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 27 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official 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
Weakness: CWE-89
Which versions are affected by CVE-2026-9617?
It affects 1 product.
Products include Dalibo Anonymizer.
How do I fix CVE-2026-9617?
No fix has been published for CVE-2026-9617 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-9617 being exploited?
There is no known exploitation of CVE-2026-9617 in the wild and no public exploit code.
Other vulnerabilities in DALIBO PostgreSQL Anonymizer
Sources
Also known as GHSA-2qfw-46cx-cgv6.