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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
Vendor Workaround
Disconnect active sessions after changing a masking rule.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/695 |
|
History
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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-10-28T17:31:48.320Z
Reserved: 2026-10-05T16:26:51.873Z
Link: CVE-2026-105617
No data.
Status : Received
Published: 2026-10-28T18:17:03.510
Modified: 2026-10-28T18:17:03.510
Link: CVE-2026-105617
No data.
OpenCVE Enrichment
Updated: 2026-10-28T18:30:15Z
Weaknesses