# CVE-2026-105618: PostgreSQL Anonymizer data masking bypass on inherited tables

Source: https://junglewise.ai/threats/cve-2026-105618-postgresql-anonymizer-s-documentation-recommends-applying-rules  
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-105618 · Severity: medium · CVSS 5.7 · Published 2026-10-28

PostgreSQL Anonymizer is a tool that masks sensitive data in PostgreSQL databases according to defined rules. When data rules are applied to partitioned or inherited tables, the masking works correctly when accessing child tables directly, but is bypassed when accessing the same data through the parent table. This allows unauthorized users with access to parent tables to view unmasked sensitive data.

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

## Quick answers

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

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

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

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

**How is CVE-2026-105618 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-105618?** 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 PostgreSQL Anonymizer 3.3.0

## Technical details

The vulnerability is a data masking bypass (CWE-693) in PostgreSQL Anonymizer's handling of table inheritance and partitioning. When anonymization rules are defined on partitioned or inherited tables, direct access to the child tables respects the masking rules, but queries through the parent table return unmasked data. This occurs due to incomplete rule propagation across the inheritance hierarchy.

## Affected products

- Dalibo PostgreSQL Anonymizer before 3.3.0

## Timeline

- 2026-10-28: disclosed

## References

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

## Related threats

- [PostgreSQL Anonymizer statistics leak in static masking](https://junglewise.ai/threats/cve-2026-110183-postgresql-anonymizer-contains-a-vulnerability-related-to-static)
- [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)