CVE-2026-105614

PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()

Published Oct 28, 2026 CVSS 3.1 · 4.7 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The function anon.image_blur() in PostgreSQL Anonymizer does not validate the declared dimensions of an input image. When a user supplies a small image that declares extremely large dimensions, the function allocates memory accordingly, potentially exceeding available RAM and causing the backend process to be OOM‑killed. This results in a cluster‑wide crash and restart, effectively denying service to all clients. The weakness is an example of unbounded memory allocation, classified as CWE‑789.

Affected Systems

The vulnerability affects the PostgreSQL Anonymizer extension developed by Dalibo. All installations of the extension prior to version 3.3.0 are affected; later releases contain the fix.

Risk and Exploitability

The CVSS score of 4.7 indicates moderate severity. EPSS is not available, so the exploit probability cannot be quantified from the data. The fix is not listed in the CISA KEV catalog. The likely attack vector is an authenticated database user that can execute SQL statements invoking anon.image_blur(); thus the vulnerability can be abused by any role with the necessary privileges. Because the function allocates memory in the backend process, memory exhaustion will affect the entire cluster once the process crashes.

Remediation

Vendor Workaround

Revoke execution rights on the range-based dummy functions or drop them.


OpenCVE Recommended Actions

  • Upgrade PostgreSQL Anonymizer to version 3.3.0 or later, which fixes the unbounded memory allocation flaw.
  • Revoke execution rights on the dummy range‑based functions or drop them as an interim workaround until the patch is applied.
  • Restrict use of anon.image_blur() to trusted roles only, limiting the ability of ordinary users to trigger memory exhaustion.

Generated by OpenCVE AI on October 28, 2026 at 18:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dalibo
Dalibo postgresql Anonymizer
Vendors & Products Dalibo
Dalibo postgresql Anonymizer
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

{'score': 4.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L'}

Weaknesses
  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 5, 2026, 4:59 PM
Reserved
Oct 5, 2026, 4:26 PM
Status
Analyzed
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 12, 2026, 1:36 PM