{"id":"CVE-2026-105614","aliases":[],"cve":{"records":[{"id":"CVE-2026-105614","source":"PostgreSQL","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-10-05T16:26:51.873Z","published":"2026-10-28T17:31:45.821Z","modified":"2026-10-28T17:31:45.821Z"}],"publishers":[{"name":"PostgreSQL","role":"CNA","organizationId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","modified":"2026-10-28T17:31:45.821Z"}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691","tags":[],"source":"PostgreSQL"}],"weaknesses":[{"id":"CWE-789","description":"Memory Allocation with Excessive Size Value","source":"PostgreSQL"}],"applicability":[],"prioritization":[]},"title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()","titleSource":"PostgreSQL","descriptionSource":"PostgreSQL","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.","score":4.7,"severity":"medium","published":"2026-10-28T17:31:45.821Z","modified":"2026-10-28T17:31:45.821Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"DALIBO","name":"PostgreSQL Anonymizer","platforms":[],"versions":[{"version":"1","status":"affected","lessThan":"3.3.0","versionType":"semver"}],"defaultStatus":"unaffected","cpes":[],"source":"PostgreSQL","url":"https://www.cve.org/CVERecord?id=CVE-2026-105614"}],"remediation":[{"text":"Revoke execution rights on the range-based dummy functions or drop them.","source":"PostgreSQL","url":"https://www.cve.org/CVERecord?id=CVE-2026-105614"}],"references":["https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691"],"sources":[{"name":"CVE","id":"CVE-2026-105614","modified":"2026-10-28T17:31:45.821Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-105614"}],"assessments":[{"source":"PostgreSQL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","score":4.7}],"sourceAffected":[],"observedAt":"2026-10-29T14:14:34.809Z","kev":{"status":"not-listed","checkedAt":"2026-10-31T03:10:30.875Z"},"coverage":[{"source":"NVD","status":"not-checked"},{"source":"GHSA","status":"not-checked"},{"source":"EUVD","status":"not-checked"},{"source":"EPSS","status":"not-checked"}],"evidence":[],"aiSummary":{"text":"PostgreSQL Anonymizer's `anon.image_blur()` function has an unbounded memory allocation weakness, allowing an attacker to exhaust backend memory. Affected versions are less than 3.3.0. This can cause a cluster-wide crash recovery.","model":"@cf/meta/llama-3.3-70b-instruct-fp8-fast","generatedAt":"2026-10-30T08:38:23.244Z","sources":[{"name":"CVE","url":"https://www.cve.org/CVERecord?id=CVE-2026-105614"}]}}