CVE-2026-110183Medium· 4.3▾ SunlitPostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pg_stats until an ANALYZE operation is performed on the table, either manua…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 23.7 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 29.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
PostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pg_stats 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.
postgresql_anonymizer >= 1 < 3.3.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Run the ANALYZE command after static masking.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-105615Low· 3.5PostgreSQL Anonymizer: Masked roles can read the statistics of masked columns in pg_stats
CVE-2026-110182Medium· 4.3PostgreSQL Anonymizer: anon.partial() and anon.partial_email() can reveal the whole data
CVE-2026-105614Medium· 4.7PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()
CVE-2026-105612Low· 3.5PostgreSQL Anonymizer: Data-modifying CTEs bypass the read-only restriction of masked roles
CVE-2026-110181Medium· 6.5PostgreSQL Anonymizer: Function declared with SQL-standard syntax leak anonymized data
CVE-2026-105616Medium· 5.7PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting