PostgreSQL Anonymizer's `anon.image_blur()` function doesn't check the declared dimension of the provided image, allowing an attacker to provide a small image with enormous declared dimensions. This vulnerability can be exploited to exhaust the memory of a backend and OOM-kill it (when ovecommit is on), which results in a cluster-wide crash recovery. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
Revoke execution rights on the range-based dummy functions or drop them.
References
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691 |
|
History
Wed, 28 Oct 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dalibo
Dalibo postgresql Anonymizer |
|
| Vendors & Products |
Dalibo
Dalibo postgresql Anonymizer |
Wed, 28 Oct 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PostgreSQL Anonymizer's `anon.image_blur()` function doesn't check the declared dimension of the provided image, allowing an attacker to provide a small image with enormous declared dimensions. This vulnerability can be exploited to exhaust the memory of a backend and OOM-kill it (when ovecommit is on), which results in a cluster-wide crash recovery. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions. | |
| Title | PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur() | |
| Weaknesses | CWE-789 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-10-28T17:31:45.821Z
Reserved: 2026-10-05T16:26:51.873Z
Link: CVE-2026-105614
No data.
Status : Received
Published: 2026-10-28T18:17:03.127
Modified: 2026-10-28T18:17:03.127
Link: CVE-2026-105614
No data.
OpenCVE Enrichment
Updated: 2026-10-28T19:00:23Z
Weaknesses