{"id":"CVE-2026-105617","title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","summary":"PostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed. Users using such plans can still see the unmasked data until the end of the session. The problem is resolved in PostgreSQL Anonymizer 3.3.0…","severity":"medium","cvss":5.7,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","cvssSource":"cna","cwe":["CWE-200"],"vendor":"DALIBO","product":"PostgreSQL Anonymizer","affected":["postgresql_anonymizer >= 1 < 3.3.0"],"published":"2026-10-28","updated":"2026-10-28","sourceUpdated":"2026-10-28T17:31:48.320Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-105617","references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}],"tags":["cve.org"],"ingestedAt":"2026-10-28T18:15:46.389Z","slug":"CVE-2026-105617","body":"## Overview\n\nPostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed. Users using such plans can still see the unmasked data until the end of the session. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.\n\n## Affected\n\n- `postgresql_anonymizer >= 1 < 3.3.0`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n### Workarounds\n\nDisconnect active sessions after changing a masking rule.","depth":"sunlit","depthScore":31,"depthScoreParts":{"impact":31.4,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}