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