Quick answers
- Is CVE-2026-105620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105620 being exploited in the wild.
- How severe is CVE-2026-105620?
- Medium severity, with a CVSS score of 6.5, published 28 October 2026.
- Which products and versions are affected?
- Dalibo PostgreSQL Anonymizer before 3.3.0.
- Is there a fix for CVE-2026-105620?
- Yes: fixed in PostgreSQL Anonymizer 3.3.0 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105620 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105620?
- 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 and later
Technical details
PostgreSQL Anonymizer fails to apply masking rules to data returned by sub-queries, resulting in information disclosure. The vulnerability affects the masking mechanism when sensitive data is accessed indirectly through a sub-query within a rule. An attacker with database query privileges can retrieve masked data in plaintext by constructing queries that return results through sub-queries.
Affected products
- Dalibo PostgreSQL Anonymizer before 3.3.0
Timeline
- 2026-10-28: disclosed