CVE-2026-120208

libheif 1.18.0 before 1.23.3 Heap Buffer Overflow via unci Mixed-Interleave Decoder

Published Oct 31, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed
Description
libheif 1.18.0 before 1.23.3 contains a heap-based buffer overflow vulnerability in unc_decoder_mixed_interleave::processTile() that allows attackers to write out of bounds by supplying chroma components with unequal bit depths. Attackers can craft a HEIF file declaring, for example, 16-bit Cb and 8-bit Cr to trigger file-controlled heap writes past the Cr plane, potentially achieving code execution in image-processing pipelines.

Analysis

AI-generated

Technical impact

The vulnerability is a heap-based buffer overflow (CWE-122) that resides in the processTile() function of the unc_decoder_mixed_interleave component of libheif versions 1.18.0 up to 1.23.2. By supplying HEIF files with chroma components that have unequal bit depths—such as a 16‑bit Cb plane and an 8‑bit Cr plane—an attacker can trigger an out‑of‑bounds write that extends beyond the Cr plane. If this write falls on executable memory, it enables the attacker to execute code within any process that loads libheif to decode the malicious file.

Affected Systems

The issue affects all applications that link to libheif from strukturag version 1.18.0 through 1.23.2, including media players, image editors, and server‑side services that process HEIF images.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity. Because the vulnerability causes a heap buffer overflow (CWE-122), the required condition for exploitation is the ability to supply a crafted HEIF file to a vulnerable instance of libheif. Based on the description, the likely attack vector is local or remote file ingestion; the attack may be triggered by any user able to provide the image to the processing pipeline. The EPSS score is < 1%, indicating a very low probability of exploitation, and the vulnerability is not currently listed in the CISA KEV catalog, which does not diminish the potential impact for affected deployments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libheif to version 1.23.3 or newer, which eliminates the off‑by‑one buffer overflow.
  • If upgrading immediately is not possible, configure the application to reject HEIF files that declare inconsistent chroma bit depths or disable the mixed‑interleave decoder if the application provides that option.
  • Add application‑level checks that validate the bit depth of all chroma components against the luma component before passing the file to libheif, preventing the out‑of‑bounds write.

Generated by OpenCVE AI on November 4, 2026 at 10:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9012-1 libheif vulnerability
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Struktur
Struktur libheif
Vendors & Products Struktur
Struktur libheif
Type Values Removed Values Added
Description libheif 1.18.0 before 1.23.3 contains a heap-based buffer overflow vulnerability in unc_decoder_mixed_interleave::processTile() that allows attackers to write out of bounds by supplying chroma components with unequal bit depths. Attackers can craft a HEIF file declaring, for example, 16-bit Cb and 8-bit Cr to trigger file-controlled heap writes past the Cr plane, potentially achieving code execution in image-processing pipelines.
Title libheif 1.18.0 before 1.23.3 Heap Buffer Overflow via unci Mixed-Interleave Decoder
Weaknesses CWE-122
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 2, 2026, 5:45 PM
Reserved
Oct 31, 2026, 11:44 AM
Status
Deferred
Published
Oct 31, 2026, 6:17 PM
Modified
Nov 2, 2026, 6:18 PM
Severity
Important
Public date
Oct 31, 2026, 5:25 PM