CVE-2026-105617

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

  • Medium 5.7

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.

Key facts

Published
28 Oct 2026
Last changed
5 Nov 2026
Assigned by
PostgreSQL
EPSS
0.217% likely to be exploited in the next 30 days, higher than 12.229% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.7CVSS 3.1, Mediumfrom the CNA (PostgreSQL)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

What to do

  • Disconnect active sessions after changing a masking rule.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
DALIBOPostgreSQL Anonymizer
  • Default status: unaffected
  • 1 up to but excluding 3.3.0 (affected)

Timeline

  1. 28 Oct 2026 Published

Weakness

References