VulnerabilityPublished 28 Oct 2026

CVE-2026-105614: DALIBO PostgreSQL Anonymizer · Excessive Memory Allocation

Affects DALIBO PostgreSQL AnonymizerSource CVE Database V5

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

Data as of 28 Oct 2026, 17:58 UTC

CVSS 3.1 base score

4.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:C/C:N/I:N/A:L

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

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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 <3.3.0 >=1	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 this vulnerability is fixed. No other mitigations are indicated or required.

Description

CVE-2026-105614 is a medium severity vulnerability in DALIBO PostgreSQL Anonymizer versions 1.0.0 up to but not including 3.3.0. The flaw exists in the anon.image_blur() function, which fails to validate the declared dimensions of an input image. An attacker can exploit this by submitting a small image with falsely large declared dimensions, causing excessive memory allocation. This can lead to backend memory exhaustion and out-of-memory (OOM) termination, triggering a cluster-wide crash recovery. The issue is fixed in version 3.3.0 and later.

Impact

Exploitation of this vulnerability leads to denial of service by exhausting backend memory resources, causing the backend process to be terminated by the operating system. This results in a cluster-wide crash recovery, impacting availability. There is no impact on confidentiality or integrity.

Summary

The vulnerability in PostgreSQL Anonymizer's anon.image_blur() function arises because it does not verify the declared size of the input image. This allows an attacker to specify a small image with artificially large dimensions, causing the function to allocate excessive memory. When the system's memory overcommit is enabled, this can exhaust backend memory and cause an OOM kill, resulting in a cluster-wide crash recovery. The flaw affects versions >=1 and <3.3.0 and is resolved in version 3.3.0.

References

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