# CVE-2026-110183: PostgreSQL Anonymizer statistics leak in static masking

Source: https://junglewise.ai/threats/cve-2026-110183-postgresql-anonymizer-contains-a-vulnerability-related-to-static  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-110183 · Severity: medium · CVSS 4.3 · Published 2026-10-28

PostgreSQL Anonymizer is a tool that masks sensitive data in databases. A vulnerability allows original data statistics to remain visible in system tables even after anonymization, potentially exposing information about the underlying data until the database performs maintenance operations. This could help attackers infer properties of sensitive data that was supposed to be hidden.

Technologies: [Dalibo PostgreSQL Anonymizer](https://junglewise.ai/threats/technologies/postgresql-anonymizer). Vendors: [Dalibo](https://junglewise.ai/threats/vendors/dalibo).

## Quick answers

**Is CVE-2026-110183 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110183 being exploited in the wild.

**How severe is CVE-2026-110183?** Medium severity, with a CVSS score of 4.3, published 28 October 2026.

**Which products and versions are affected?** Dalibo PostgreSQL Anonymizer before 3.3.0.

**Is there a fix for CVE-2026-110183?** Yes: fixed in 3.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-110183 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-110183?** Check whether you run Dalibo PostgreSQL Anonymizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.3.0

## Technical details

PostgreSQL Anonymizer's static masking feature fails to clear accumulated statistics (pg_stats) when masking data, leaving metadata about the original unmasked data visible. An attacker with database access can examine statistical information to infer properties of sensitive data. The leak persists until an ANALYZE operation is manually executed or triggered by autovacuum, which rebuilds statistics based on masked data.

## Affected products

- Dalibo PostgreSQL Anonymizer before 3.3.0

## Timeline

- 2026-10-28: disclosed

## References

- [https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/722](https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/722)

## Related threats

- [PostgreSQL Anonymizer information disclosure in partial() functions](https://junglewise.ai/threats/cve-2026-110182-postgresql-anonymizer-contains-a-vulnerability-related-to-the)
- [PostgreSQL Anonymizer SQL-standard function body bypass](https://junglewise.ai/threats/cve-2026-110181-postgresql-anonymizer-contains-a-vulnerability-related-to)
- [PostgreSQL Anonymizer data masking bypass in sub-query rules](https://junglewise.ai/threats/cve-2026-105620-postgresql-anonymizer-doesn-t-mask-data-returned-by-a-sub-query)
- [PostgreSQL Anonymizer data masking bypass in security_invoker views](https://junglewise.ai/threats/cve-2026-105619-postgresql-anonymizer-doesn-t-mask-data-accessed-thru-a-security)
- [PostgreSQL Anonymizer data masking bypass on inherited tables](https://junglewise.ai/threats/cve-2026-105618-postgresql-anonymizer-s-documentation-recommends-applying-rules)