VulnerabilityPublished 28 Oct 2026

CVE-2026-105616: 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:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 PostgreSQL Anonymizer to version 3.3.0 or later, where the exposure of salt and shift parameters in system catalogs is fixed.

Description

CVE-2026-105616 is a vulnerability in DALIBO PostgreSQL Anonymizer versions prior to 3.3.0 where sensitive information (salt and shift values) can be exposed to unauthorized users. Although PostgreSQL restricts access to these values via the SHOW command for non-privileged users, they remain visible in system catalogs such as pg_db_role_setting or pg_roles if set at the database or user level. This exposure could allow unauthorized actors with limited privileges to obtain sensitive anonymization parameters. The issue is fixed in PostgreSQL Anonymizer version 3.3.0 and later.

Impact

Unauthorized users with limited privileges can access sensitive anonymization parameters (salt and shift) by querying system catalogs, potentially undermining the anonymization process. The confidentiality of anonymized data could be compromised, but there is no indication of integrity or availability impact. The CVSS 3.1 base score is 5.7 (medium severity), reflecting network attack vector, low attack complexity, required privileges, and no user interaction.

References

gitlab.com/dalibo/postgresql_anonymizer/-/issues/694 (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