Skip to content
Heist/ feed
Back to feed
Medium

PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()

Type: advisorySources: Official CVE List

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.

Products
PostgreSQL Anonymizer
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-105614
Confirmed fixed CVEs
Not specified
Updated in this feed
1 Nov 2026, 20:25 UTC · Revision 1

Source evidence

PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()

core-cve · Original source

Published 28 Oct 2026, 17:31 UTC

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.

cve:CVE-2026-105614

PostgreSQL Anonymizer

Fixed versions: Not specified

Complete source record
{
  "id": "411d041482463e215de12aabd4c529cede9e1828e70ad820db8c28dbf0dd0d85",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-105614",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()",
    "summary": "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.",
    "evidence": "cve:CVE-2026-105614",
    "products": [
      {
        "name": {
          "value": "PostgreSQL Anonymizer",
          "evidence": "/containers/cna/affected/0/product"
        },
        "prerequisites": [],
        "fixed_versions": [],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-105614",
      "aliases": [
        "CVE-2026-105614"
      ],
      "metrics": [
        {
          "format": "CVSS",
          "cvssV3_1": {
            "version": "3.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"
          }
        }
      ],
      "affected": [
        {
          "vendor": "DALIBO",
          "product": "PostgreSQL Anonymizer",
          "versions": [
            {
              "status": "affected",
              "version": "1",
              "lessThan": "3.3.0",
              "versionType": "semver"
            }
          ],
          "defaultStatus": "unaffected"
        }
      ],
      "modified": "2026-10-28T17:31:45.821Z",
      "provider": "cve",
      "references": [
        "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/691"
      ],
      "provider_metadata": {
        "cna": {
          "orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007",
          "shortName": "PostgreSQL",
          "dateUpdated": "2026-10-28T17:31:45.821Z"
        }
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-105614",
        "evidence": "/cveMetadata/cveId"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/containers/cna/metrics"
  },
  "source_id": "core-cve",
  "document_id": 466512,
  "published_at": "2026-10-28T17:31:45.821+00:00"
}