{
  "affected": [
    {
      "affectedData": [
        {
          "product": "libheif",
          "vendor": "strukturag",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 1.22.0"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, when decoding a HEIF grid image with strict_decoding=false (the default), a corrupted tile silently fails to decode and the library returns heif_error_Ok with no indication of failure, leading to an uninitialized heap memory information leak. The canvas is allocated via create_clone_image_at_new_size() \u2192 plane.alloc() \u2192 new (std::nothrow) uint8_t[allocation_size] which does not zero the memory; only the alpha plane is explicitly initialized via fill_plane(), so the Y, Cb, and Cr planes contain whatever was previously at that heap address. The failed tile\u0027s region of the canvas is never written. It retains uninitialized heap data that is delivered to the caller as decoded pixel values (4,096 bytes per Y/Cb/Cr plane = 12,288+ bytes total). Any application using libheif to decode grid-based HEIF/AVIF files with default settings is vulnerable: a crafted .heic or .avif file causes 4,096+ bytes of heap memory to appear as pixel values in the decoded image, and the calling application receives heif_error_Ok, so it has no indication the output contains heap garbage. In server-side image processing, an uploaded crafted HEIF decoded and re-encoded (e.g., as PNG/JPEG for thumbnails, CDN, social media) can leak cross-user data such as auth tokens, database results, and other users\u0027 image data. This issue has been fixed in version 1.22.0."
    },
    {
      "lang": "es",
      "value": "libheif es un decodificador y codificador de formato de archivo HEIF y AVIF. En las versiones 1.21.2 y anteriores, al decodificar una imagen de cuadr\u00edcula HEIF con strict_decoding=false (el valor predeterminado), un mosaico corrupto falla silenciosamente al decodificarse y la biblioteca devuelve heif_error_Ok sin ninguna indicaci\u00f3n de fallo, lo que lleva a una fuga de informaci\u00f3n de memoria de pila no inicializada. El lienzo se asigna a trav\u00e9s de create_clone_image_at_new_size() ? plane.alloc() ? new (std::nothrow) uint8_t[allocation_size] que no pone a cero la memoria; solo el plano alfa se inicializa expl\u00edcitamente a trav\u00e9s de fill_plane(), por lo que los planos Y, Cb y Cr contienen lo que estuviera previamente en esa direcci\u00f3n de pila. La regi\u00f3n del lienzo correspondiente al mosaico fallido nunca se escribe. Retiene datos de pila no inicializados que se entregan al llamador como valores de p\u00edxel decodificados (4.096 bytes por plano Y/Cb/Cr = 12.288+ bytes en total). Cualquier aplicaci\u00f3n que utilice libheif para decodificar archivos HEIF/AVIF basados en cuadr\u00edcula con la configuraci\u00f3n predeterminada es vulnerable: un archivo .heic o .avif manipulado hace que 4.096+ bytes de memoria de pila aparezcan como valores de p\u00edxel en la imagen decodificada, y la aplicaci\u00f3n que llama recibe heif_error_Ok, por lo que no tiene ninguna indicaci\u00f3n de que la salida contenga basura de pila. En el procesamiento de im\u00e1genes del lado del servidor, un HEIF manipulado subido, decodificado y recodificado (por ejemplo, como PNG/JPEG para miniaturas, CDN, redes sociales) puede filtrar datos entre usuarios, como tokens de autenticaci\u00f3n, resultados de base de datos y datos de imagen de otros usuarios. Este problema ha sido solucionado en la versi\u00f3n 1.22.0."
    }
  ],
  "id": "CVE-2026-32814",
  "lastModified": "2026-07-24T09:10:00.153",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 3.6,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-32814",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-05-20T14:05:19.872878Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-05-19T21:16:42.223",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/strukturag/libheif/releases/tag/v1.22.0"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-4m8r-34pg-rvwc"
    },
    {
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-4m8r-34pg-rvwc"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-200"
        },
        {
          "lang": "en",
          "value": "CWE-908"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}