CVE-2026-110183: PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking
PostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pgstats until an ANALYZE operation is performed on the table, either manually or by autovacuum. This issue is fixed in PostgreSQL Anonymizer 3.3.0 and later versions.
Affected Software
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
Frequently Asked Questions
Who can exploit this issue?
An attacker needs low-privileged access to the PostgreSQL instance and the ability to view the relevant statistics in pg_stats. The exposed information is limited to statistics derived from the original data; confidentiality impact is rated low.
When are stale original-data statistics exposed?
They remain visible after static masking until ANALYZE runs on the affected table. ANALYZE may be run manually, or autovacuum may perform it.
What can be done if upgrading is not immediately possible?
Run ANALYZE on tables after applying static masking to replace statistics associated with the original data. Ensure autovacuum is allowed to analyze the affected tables.
How can I determine whether an environment is affected?
Review pg_stats for tables that have undergone static masking and check whether ANALYZE has run since masking. PostgreSQL Anonymizer 3.3.0 and later include the fix.