# CVE-2026-11945: PostgreSQL Anonymizer: SQL injection in the rules import functions

> A SQL injection vulnerability in PostgreSQL Anonymizer allows attackers to execute malicious code with superuser privileges via crafted JSON imports.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/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:** 11 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-g5vm-7gwv-45rj

## What is CVE-2026-11945?

CVE-2026-11945 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Jun 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 JSON document and placing malicious code inside a particular key-value pair. If a superuser calls the import_database_rules() or import_roles_rules() functions, the malicious code is executed with superuser privileges. The problem is resolved in PostgreSQL Anonymizer 3.1.1 and further versions

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Dalibo Postgresql Anonymizer.

## How do I fix CVE-2026-11945?

No fix has been published for CVE-2026-11945 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11945 being exploited?

There is no known exploitation of CVE-2026-11945 in the wild and no public exploit code.

## Other vulnerabilities in DALIBO PostgreSQL Anonymizer

- [CVE-2026-13455](https://insights.sbomify.com/CVE-2026-13455/): PostgreSQL Anonymizer: Unrestricted function can leak the secret salt (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11945 is a medium-severity SQL injection vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Jun 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-11945 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-11945/ (Markdown: https://insights.sbomify.com/CVE-2026-11945/index.md)
```

## Sources

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

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