{"api_version":"1","generated_at":"2026-10-29T04:49:35+00:00","cve":"CVE-2026-105614","urls":{"html":"https://cve.report/CVE-2026-105614","api":"https://cve.report/api/cve/CVE-2026-105614.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-105614","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-105614"},"summary":{"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.","state":"PUBLISHED","assigner":"PostgreSQL","published_at":"2026-10-28 18:17:03","updated_at":"2026-10-28 18:17:03"},"problem_types":["CWE-789","CWE-789 Memory Allocation with Excessive Size Value"],"metrics":[{"version":"3.1","source":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","type":"Secondary","score":"4.7","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","data":{"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","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"CHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"LOW"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"4.7","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","data":{"baseScore":4.7,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","version":"3.1"}}],"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691","name":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691","refsource":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-105614","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105614","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"DALIBO","product":"PostgreSQL Anonymizer","version":"affected 1 3.3.0 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[{"source":"CNA","title":"","value":"Revoke execution rights on the range-based dummy functions or drop them.","time":"","lang":"en"}],"exploits":[],"credits":[{"source":"CNA","value":"The PostgreSQL Anonymizer project thanks user Alexander Kukushkin for reporting this problem.","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"PostgreSQL Anonymizer","vendor":"DALIBO","versions":[{"lessThan":"3.3.0","status":"affected","version":"1","versionType":"semver"}]}],"credits":[{"lang":"en","value":"The PostgreSQL Anonymizer project thanks user Alexander Kukushkin for reporting this problem."}],"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."}],"metrics":[{"cvssV3_1":{"baseScore":4.7,"baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","version":"3.1"},"format":"CVSS"}],"problemTypes":[{"descriptions":[{"cweId":"CWE-789","description":"Memory Allocation with Excessive Size Value","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-28T17:31:45.821Z","orgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","shortName":"PostgreSQL"},"references":[{"url":"https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691"}],"title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()","workarounds":[{"lang":"en","value":"Revoke execution rights on the range-based dummy functions or drop them."}]}},"cveMetadata":{"assignerOrgId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","assignerShortName":"PostgreSQL","cveId":"CVE-2026-105614","datePublished":"2026-10-28T17:31:45.821Z","dateReserved":"2026-10-05T16:26:51.873Z","dateUpdated":"2026-10-28T17:31:45.821Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 18:17:03","lastModifiedDate":"2026-10-28 18:17:03","problem_types":["CWE-789","CWE-789 Memory Allocation with Excessive Size Value"],"metrics":{"cvssMetricV31":[{"source":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","type":"Secondary","cvssData":{"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","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"CHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"LOW"},"exploitabilityScore":2.8,"impactScore":1.4}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"105614","Ordinal":"1","Title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation ","CVE":"CVE-2026-105614","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"105614","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"PostgreSQL Anonymizer: Unbounded image-decode memory allocation "}]}}}