Quick answers
- Is CVE-2026-105616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105616 being exploited in the wild.
- How severe is CVE-2026-105616?
- 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-105616?
- 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-105616 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105616?
- 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's salt and shift parameters are intended to be restricted from unprivileged users via the SHOW command, but this restriction is incomplete: users can still query pg_db_role_setting and pg_roles system catalog tables to retrieve these values if they were set at the database or role level. An authenticated attacker without pg_read_all_settings membership can access system catalogs directly to obtain these parameters, circumventing the intended access control and potentially enabling anonymization bypass attacks.
Affected products
- Dalibo PostgreSQL Anonymizer before 3.3.0
Timeline
- 2026-10-28: disclosed
- 2026-10-28: advisory