# CVE-2026-2361: Privilege escalation in PostgreSQL Anonymizer

> Users with CREATE privileges can gain superuser access by exploiting improper search_path handling in the PostgreSQL Anonymizer extension.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** GHSA-xcpc-ffvj-qvhw, UBUNTU-CVE-2026-2361

## What is CVE-2026-2361?

CVE-2026-2361 is a high-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a temporary view based on a function containing malicious code. When the anon.get_tablesample_ratio function is then called, the malicious code is executed with superuser privileges. This privilege elevation can be exploited by users having the CREATE privilege in PostgreSQL 15 and later. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version because the creation permission on the public schema is granted by default. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-2361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2361 is a high-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 11 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2361 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-2361/ (Markdown: https://insights.sbomify.com/CVE-2026-2361/index.md)
```

## Sources

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

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