CVE-2026-105614

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

  • Medium 4.7

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.

Key facts

Published
28 Oct 2026
Last changed
5 Nov 2026
Assigned by
PostgreSQL
EPSS
0.183% likely to be exploited in the next 30 days, higher than 7.956% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.7CVSS 3.1, Mediumfrom the CNA (PostgreSQL)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L

What to do

  • Revoke execution rights on the range-based dummy functions or drop them.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
DALIBOPostgreSQL Anonymizer
  • Default status: unaffected
  • 1 up to but excluding 3.3.0 (affected)

Timeline

  1. 28 Oct 2026 Published

Weakness

References