CVE-2025-5690VulnerabilityPublished 4 Jun 2025

CVE-2025-5690: DALIBO PostgreSQL Anonymizer · Information Exposure

Affects DALIBO PostgreSQL AnonymizerSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.2.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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 4 Jun 2025
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 2026-10-25.

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 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 dalibo/postgresql_anonymizer to 2.2.1.

Affected software

Product	Affected	Fixed in
GitHubdalibo/postgresql_anonymizer`pkg:github/dalibo/postgresql_anonymizer`Other threats	Affected =1 =2.0 =2.1 <2.2.1	Fixed in 2.2.1

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

AI-suggested

European organizations should immediately verify if they are using PostgreSQL Anonymizer versions 2.0 or 2.1 with dynamic masking enabled. If so, upgrading to version 2.2.1 or later is critical to remediate the vulnerability. Organizations should audit database user privileges to ensure that only necessary users have access to masked data and that privilege escalation paths are closed. Implement strict access controls and monitor database activities for unusual cursor usage or pg_dump operations that could indicate exploitation attempts. Additionally, consider disabling dynamic masking if it is not essential, as this reduces the attack surface. Regularly review and update anonymization policies and test them against bypass techniques. Employ database activity monitoring (DAM) tools to detect anomalous queries or data access patterns. Finally, ensure that incident response plans include procedures for data exposure incidents related to anonymization failures.

Description

PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1

Impact

For European organizations, the exposure of sensitive data due to this vulnerability can have serious consequences. Many European entities use PostgreSQL databases for storing personal and sensitive information, often under strict regulatory frameworks such as GDPR. The ability for a masked user to bypass anonymization and access original data could lead to unauthorized disclosure of personal data, resulting in privacy breaches, regulatory fines, reputational damage, and loss of customer trust. The impact is particularly critical for sectors handling highly sensitive information, such as healthcare, finance, and government services. Since dynamic masking is not enabled by default, the risk is somewhat mitigated; however, organizations that have enabled this feature for enhanced data protection are directly at risk. The vulnerability does not affect data integrity or availability but compromises confidentiality, which is a core requirement under European data protection laws. Additionally, the requirement for some level of privileges means insider threats or compromised accounts could exploit this vulnerability more easily. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future attacks.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 03:56 UTC

Technical details

References

Community reviews

Related threats