{"id":"CVE-2026-105617","aliases":["EUVD-2026-112289","GHSA-pmmg-m528-xf29"],"status":"published","title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","description":"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.","severity":{"version":"3.1","score":5.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00217,"percentile":0.12263,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-200"],"published":"2026-10-28T17:31:48Z","modified":"2026-11-10T21:47:29Z","products":[{"vendor":"dalibo","product":"postgresql anonymizer"},{"vendor":"dalibo","product":"postgresql_anonymizer"}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695","tags":["Broken Link","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105617","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-pmmg-m528-xf29"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/105xxx/CVE-2026-105617.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-105617","title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","description":"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.","status":"published","published":"2026-10-28T17:31:48.32Z","modified":"2026-11-05T16:58:16.605Z","cvss":[{"version":"3.1","score":5.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-200"],"updated_at":"2026-11-05T18:54:20.702128Z"}],"euvd":[{"id":"EUVD-2026-112289","description":"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.","status":"published","published":"2026-10-28T17:31:48Z","modified":"2026-11-05T16:58:16Z","cvss":[{"version":"3.1","score":5.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-05T18:00:57.218327Z"}],"ghsa":[{"id":"GHSA-pmmg-m528-xf29","title":"PostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed....","description":"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.","status":"published","published":"2026-10-28T18:32:10Z","modified":"2026-10-28T18:32:15Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:14:35.861264Z"}],"nvd":[{"id":"CVE-2026-105617","description":"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.","status":"published","published":"2026-10-28T18:17:03.51Z","modified":"2026-11-12T13:37:28.47Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-200"],"updated_at":"2026-11-11T00:21:51.751326Z"}],"osv":[{"id":"CVE-2026-105617","title":"PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule","description":"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.","status":"published","published":"2026-10-28T17:31:48.32Z","modified":"2026-11-12T02:46:49.279849827Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","level":"medium"}],"cwes":["CWE-200"],"updated_at":"2026-11-07T03:07:59.773479Z"}]}}