{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-105617","assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","state":"PUBLISHED","assignerShortName":"PostgreSQL","dateReserved":"2026-10-05T16:26:51.873Z","datePublished":"2026-10-28T17:31:48.320Z","dateUpdated":"2026-10-28T17:31:48.320Z"},"containers":{"cna":{"providerMetadata":{"orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","shortName":"PostgreSQL","dateUpdated":"2026-10-28T17:31:48.320Z"},"title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","descriptions":[{"lang":"en","value":"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 and later versions."}],"affected":[{"defaultStatus":"unaffected","product":"PostgreSQL Anonymizer","vendor":"DALIBO","versions":[{"lessThan":"3.3.0","status":"affected","version":"1","versionType":"semver"}]}],"problemTypes":[{"descriptions":[{"lang":"en","cweId":"CWE-200","type":"CWE","description":"Exposure of Sensitive Information to an Unauthorized Actor"}]}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695"}],"metrics":[{"format":"CVSS","cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","baseScore":5.7,"baseSeverity":"MEDIUM"}}],"workarounds":[{"lang":"en","value":"Disconnect active sessions after changing a masking rule."}],"credits":[{"lang":"en","value":"The PostgreSQL Anonymizer project thanks user Ilya Staroverov for reporting this problem."}]}}}