# 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.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **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 available:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-2qfw-46cx-cgv6

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-9617?

It affects 1 product.


Products: 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.

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

- [CVE-2024-2338](https://insights.sbomify.com/CVE-2024-2338/): SQL Injection in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule (high 8.0)
- [CVE-2024-2339](https://insights.sbomify.com/CVE-2024-2339/): Improper Input Validation in PostgreSQL Anonymizer 1.2 allows table owner to gain superuser privileges via masking rule (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9617 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-9617 in the wild and no public exploit code.

Affected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9617/ (Markdown: https://insights.sbomify.com/CVE-2026-9617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9617
- OSV: https://osv.dev/vulnerability/CVE-2026-9617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9617/
Summaries are generated and may contain mistakes; the official description above is the record.