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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695 |
|
History
Wed, 28 Oct 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dalibo
Dalibo postgresql Anonymizer |
|
| Vendors & Products |
Dalibo
Dalibo postgresql Anonymizer |
Wed, 28 Oct 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule | |
| Weaknesses | CWE-200 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published: 2026-10-28T17:31:48.320Z
Updated: 2026-10-28T17:31:48.320Z
Reserved: 2026-10-05T16:26:51.873Z
Link: CVE-2026-105617
No data.
Status : Awaiting Analysis
Published: 2026-10-28T18:17:03.510
Modified: 2026-10-29T15:29:45.363
Link: CVE-2026-105617
No data.
ReportizFlow