# CVE-2026-110183: PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5fhp-486m-m23r

## What is CVE-2026-110183?

CVE-2026-110183 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026. 

### Official description

PostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pg_stats until an ANALYZE operation is performed on the table, either manually or by autovacuum. This issue is fixed in PostgreSQL Anonymizer 3.3.0 and later versions.

Weakness: CWE-202 (Exposure of Sensitive Information Through Data Queries)

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


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

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

## Is CVE-2026-110183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110183 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110183 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-110183/ (Markdown: https://insights.sbomify.com/CVE-2026-110183/index.md)
```

## Sources

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

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