{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-105614","assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","state":"PUBLISHED","assignerShortName":"PostgreSQL","dateReserved":"2026-10-05T16:26:51.873Z","datePublished":"2026-10-28T17:31:45.821Z","dateUpdated":"2026-10-28T17:31:45.821Z"},"containers":{"cna":{"providerMetadata":{"orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","shortName":"PostgreSQL","dateUpdated":"2026-10-28T17:31:45.821Z"},"title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()","descriptions":[{"lang":"en","value":"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."}],"affected":[{"defaultStatus":"unaffected","product":"PostgreSQL Anonymizer","vendor":"DALIBO","versions":[{"lessThan":"3.3.0","status":"affected","version":"1","versionType":"semver"}]}],"problemTypes":[{"descriptions":[{"lang":"en","cweId":"CWE-789","type":"CWE","description":"Memory Allocation with Excessive Size Value"}]}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691"}],"metrics":[{"format":"CVSS","cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","baseScore":4.7,"baseSeverity":"MEDIUM"}}],"workarounds":[{"lang":"en","value":"Revoke execution rights on the range-based dummy functions or drop them."}],"credits":[{"lang":"en","value":"The PostgreSQL Anonymizer project thanks user Alexander Kukushkin for reporting this problem."}]}}}