CVE-2026-105618Medium· 5.7▾ SunlitPostgreSQL Anonymizer's documentation recommends applying rules on partitions and inheritance tables. Direct access to the paritions / inheritance tables is masked but not thru the parent table. The problem is resolved in PostgreSQL Anon…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 31.4 · 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's documentation recommends applying rules on partitions and inheritance tables. Direct access to the paritions / inheritance tables is masked but not thru the parent table. The problem is resolved 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.
None
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-105612Low· 3.5PostgreSQL Anonymizer: Data-modifying CTEs bypass the read-only restriction of masked roles
CVE-2026-105620Medium· 6.5PostgreSQL Anonymizer: A masked role reads the authentic data of masked tables through a masking rule with a sub-query
CVE-2026-105619Medium· 4.8PostgreSQL Anonymizer: Masking rules of the tables are not applied through security_invoker views
CVE-2026-105614Medium· 4.7PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()
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