{"id":"CVE-2026-105614","state":"PUBLISHED","title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()","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.","publishedAt":"2026-10-28T17:31:45.821Z","updatedAt":"2026-10-28T17:31:45.821Z","severity":{"score":4.7,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","source":"PostgreSQL"},"assigner":"PostgreSQL","products":["DALIBO PostgreSQL Anonymizer"],"affected":[{"vendor":"DALIBO","product":"PostgreSQL Anonymizer","defaultStatus":"unaffected","versions":[{"version":"1","status":"affected","lessThan":"3.3.0","versionType":"semver"}]}],"references":["https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691"],"weaknesses":["CWE-789"],"ingestedAt":"2026-10-29T20:10:23.711Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/105xxx/CVE-2026-105614.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-105614","state":"PUBLISHED","datePublished":"2026-10-28T17:31:45.821Z","dateUpdated":"2026-10-28T17:31:45.821Z","assignerShortName":"PostgreSQL","assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","dateReserved":"2026-10-05T16:26:51.873Z"},"containers":{"cna":{"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":[{"vendor":"DALIBO","product":"PostgreSQL Anonymizer","defaultStatus":"unaffected","versions":[{"version":"1","status":"affected","lessThan":"3.3.0","versionType":"semver"}]}],"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"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-789","lang":"en","type":"CWE","description":"Memory Allocation with Excessive Size Value"}]}],"providerMetadata":{"shortName":"PostgreSQL","orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","dateUpdated":"2026-10-28T17:31:45.821Z"},"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."}]}}}}