VulnerabilityPublished 28 Oct 2026

CVE-2026-105617: DALIBO PostgreSQL Anonymizer · Information Exposure

Affects DALIBO PostgreSQL AnonymizerSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium : upgrade to 3.3.0 when convenient.

Data as of 28 Oct 2026, 17:58 UTC

CVSS 3.1 base score

5.7Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 3.3.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade PostgreSQL Anonymizer and dalibo/postgresql_anonymizer to 3.3.0.

Affected software

Product	Affected	Fixed in
DALIBOPostgreSQL Anonymizer	Affected >=1 <3.3.0	Fixed in 3.3.0
GitHubdalibo/postgresql_anonymizer`pkg:github/dalibo/postgresql_anonymizer`Other threats	Affected >=1 <3.3.0	Fixed in 3.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to PostgreSQL Anonymizer version 3.3.0 or later, where the issue is fixed by invalidating prepared plans after rule or role changes. No other mitigation is indicated or required.

Description

CVE-2026-105617 is a vulnerability in DALIBO PostgreSQL Anonymizer versions prior to 3.3.0 where prepared plans are not invalidated after a rule addition or role change. This allows users to access unmasked sensitive data until the session ends. The issue is fixed in version 3.3.0.

Impact

Unauthorized users can access sensitive information that should have been anonymized by the PostgreSQL Anonymizer when using prepared plans created before rule or role changes. This leads to exposure of confidential data until the session ends. There is no indication of integrity or availability impact. The CVSS score is 5.7 (medium severity), reflecting the network attack vector, low complexity, no privileges required, and user interaction needed.

Summary

The PostgreSQL Anonymizer did not invalidate prepared query plans after changes such as adding a rule or modifying a user role. As a result, users executing these prepared plans could see unmasked sensitive information during their session, bypassing intended anonymization controls. This vulnerability affects all versions from 1 up to but not including 3.3.0. The issue was resolved in version 3.3.0 by ensuring that prepared plans are invalidated appropriately to prevent exposure of unmasked data.

References

gitlab.com/dalibo/postgresql_anonymizer/-/issues/695 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 17:58 UTC

Technical details

References

Community reviews

Related threats