CVE-2026-105617

PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule

Published Oct 28, 2026 CVSS 3.1 · 5.7 Medium EPSS < 1% KEV · Not listed
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

AI-generated

Technical impact

The vulnerability allows a prepared statement cached before a masking rule addition or role change to bypass PostgreSQL Anonymizer’s dynamic masking, exposing previously hidden data until the session ends. This constitutes a confidentiality breach as data intended for masking may be disclosed. The weakness matches CWE-200, highlighting inadequate protection of information. The CVSS score of 5.7 indicates moderate severity.

Affected Systems

Dalibo PostgreSQL Anonymizer is affected in all releases prior to version 3.3.0. Users running any older version without the patch risk that cached plans could reveal sensitive data after role changes or new masking rules are applied.

Risk and Exploitability

The CVSS score of 5.7 reflects moderate impact, and with no EPSS score available the likelihood of exploitation is uncertain but not negligible. The vulnerability can be exploited by an attacker who can influence or observe sessions that rely on prepared statements, such as by adding masking rules or altering roles, thereby causing cached plans to persist and expose unmasked data. The issue is not listed in CISA KEV, so no confirmed exploits are reported yet.

Remediation

Vendor Workaround

Disconnect active sessions after changing a masking rule.


OpenCVE Recommended Actions

  • Upgrade PostgreSQL Anonymizer to version 3.3.0 or newer to eliminate the plan caching issue.
  • After any role change or the creation of a new masking rule, disconnect all active sessions so that cached prepared plans are cleared.
  • Avoid using cached prepared statements in environments where masking rules or roles may change; create new plans after such changes to ensure masking is applied.

Generated by OpenCVE AI on October 28, 2026 at 18:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dalibo
Dalibo postgresql Anonymizer
Vendors & Products Dalibo
Dalibo postgresql Anonymizer
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

{'score': 5.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 5, 2026, 4:58 PM
Reserved
Oct 5, 2026, 4:26 PM
Status
Analyzed
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 12, 2026, 1:37 PM