{"id":"CVE-2026-105614","kind":"vulnerability","aliases":["CVE-2026-105614"],"related":[],"title":"PostgreSQL Anonymizer: image_blur accepts oversized image dimensions, exhausting memory","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.","summary":"The anon.image_blur() function in PostgreSQL Anonymizer does not check the declared dimensions of an input image, so a small file claiming huge dimensions can be supplied. Processing it can exhaust backend memory, causing the out-of-memory killer to terminate the backend and trigger a cluster-wide crash recovery.","severity":"medium","cvss":4.7,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["database","package","postgresql","postgresql-anonymizer","self-hosted"],"not_affected_if":["extension-not-installed","fixed-version","image-blur-unused"],"how_to_check":"- Run `SELECT extversion FROM pg_extension WHERE extname = 'anon';` in each database where the extension is installed and compare against `3.3.0`.\n- Check whether the `anon.image_blur` function is used by application code or any SQL you run.","fix":"- Upgrade PostgreSQL Anonymizer to `3.3.0` or later.","status":"open","published_at":"2026-10-28T18:17:03+00:00","first_seen_at":"2026-10-28T18:34:32+00:00","triaged_at":"2026-10-28T18:35:09+00:00","updated_at":"2026-10-28T18:35:09+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-10-28T18:35:09Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade PostgreSQL Anonymizer to `3.3.0` or later.","reach":"unknown","title":"PostgreSQL Anonymizer: image_blur accepts oversized image dimensions, exhausting memory","impact":"medium","summary":"The anon.image_blur() function in PostgreSQL Anonymizer does not check the declared dimensions of an input image, so a small file claiming huge dimensions can be supplied. Processing it can exhaust backend memory, causing the out-of-memory killer to terminate the backend and trigger a cluster-wide crash recovery.","category":"package","nicknames":[],"who_cares":["postgresql","postgresql-anonymizer","self-hosted","database"],"confidence":0.6,"needs_auth":"unknown","worst_case":"A backend is OOM-killed, forcing cluster-wide crash recovery and downtime.","analyst_note":"","how_to_check":"- Run `SELECT extversion FROM pg_extension WHERE extname = 'anon';` in each database where the extension is installed and compare against `3.3.0`.\n- Check whether the `anon.image_blur` function is used by application code or any SQL you run.","needs_analyst":false,"not_affected_if":["extension-not-installed","fixed-version","image-blur-unused"],"who_is_affected":"Only deployments that have the PostgreSQL Anonymizer extension installed and call anon.image_blur() on image data, typically during data masking or anonymization jobs. Systems that do not install the extension, or that run versions 3.3.0 and later, are not affected. Exposure is mainly a concern where untrusted users can supply images that reach that function.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"unknown"},"cost_usd":0.000641,"input_tokens":3379,"output_tokens":607,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-105614':13A,16A '-2026':12A,15A '3.3.0':143C 'accept':5A 'allow':94C 'anon.image':27B,81C 'anonym':2A,22B,32B,79C,142C 'attack':96C 'backend':57B,69B,117C 'blur':4A,28B,82C 'caus':59B 'check':35B,86C 'claim':47B 'cluster':74B,132C 'cluster-wid':73B,131C 'crash':76B,134C 'cve':11A,14A 'databas':17B 'declar':37B,88C,104C 'dimens':8A,38B,49B,89C,105C 'doesn':84C 'enorm':103C 'exhaust':9A,56B,112C 'exploit':110C 'file':46B 'function':29B,83C 'host':25B 'huge':48B 'imag':3A,7A,42B,93C,101C 'input':41B 'kill':121C 'killer':65B 'later':145C 'memori':10A,58B,64B,114C 'oom':120C 'oom-kil':119C 'out-of-memori':61B 'ovecommit':124C 'overs':6A 'packag':18B 'postgresql':1A,19B,21B,31B,78C,141C 'postgresql-anonym':20B 'problem':137C 'process':53B 'provid':92C,98C 'recoveri':77B,135C 'resolv':139C 'result':128C 'self':24B 'self-host':23B 'small':45B,100C 'suppli':52B 'termin':67B 'trigger':71B 'version':146C 'vulner':107C 'wide':75B,133C","nicknames":[],"mitigations":[],"who_affected":"Only deployments that have the PostgreSQL Anonymizer extension installed and call anon.image_blur() on image data, typically during data masking or anonymization jobs. Systems that do not install the extension, or that run versions 3.3.0 and later, are not affected. Exposure is mainly a concern where untrusted users can supply images that reach that function.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-28T18:17:03+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L","cvss_by":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-105614","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-105614","severity":null,"published_at":"2026-10-28T18:17:03+00:00","modified_at":"2026-10-28T18:17:03+00:00","first_seen_at":"2026-10-28T18:34:32+00:00","fetched_at":"2026-10-28T18:34:32+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}