CVE-2026-105620: PostgreSQL Anonymizer: A masked role reads the authentic data of masked tables through a masking rule with a sub-query
Published Oct 28, 2026
·Updated
PostgreSQL Anonymizer doesn't mask data returned by a sub-query in a rule. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
Affected Software
1 affected component
PostgreSQL Anonymizer PostgreSQL Anonymizer<3.3.0
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PostgreSQL Anonymizerto a version that resolves this vulnerability.Fixed in 3.3.0
Event History
Oct 28, 2026
CVE Published
via MITRE·05:31 PM
Data Sourced
via MITRE·05:31 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
Who can exploit this issue?
A masked role can exploit it when it can read from a masked table through a rule that uses a sub-query. The attacker must already have the privileges associated with that masked role.
2
Are deployments running PostgreSQL Anonymizer 3.3.0 or later affected?
No. The issue is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
3
How can I identify potentially affected configurations?
Review rules associated with masked tables for sub-queries, and determine whether masked roles can read data through those rules. Such paths may return authentic data rather than masked results.