# CVE-2026-62292: libheif: Out-of-bounds read in uncompressed unci tile range slicing

> An integer overflow in libheif allows attackers to cause a denial of service via a crafted HEIF image requiring tile decoding.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** BELL-CVE-2026-62292, DEBIAN-CVE-2026-62292, ECHO-8e41-0efd-8249, GHSA-73p7-m7gg-w2jv, MINI-fmc3-5ghj-rw37, ROOT-OS-DEBIAN-11-CVE-2026-62292, ROOT-OS-DEBIAN-12-CVE-2026-62292, UBUNTU-CVE-2026-62292, USN-8649-1

## What is CVE-2026-62292?

CVE-2026-62292 is a high-severity vulnerability in strukturag libheif, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.1, a crafted uncompressed HEIF image using generic zlib unci full-item compression can crash an application that decodes an advertised tile with heif_image_handle_decode_image_tile(). In libheif/codecs/uncompressed/unc_decoder.cc, unc_decoder::fetch_tile_data() computes a large tile offset and unc_decoder::get_compressed_image_data_uncompressed() validates it with range_start_offset plus range_size. For the last advertised tile (4095, 4095), the addition can wrap to zero, bypass the bounds check, and pass an invalid source pointer and a one-terabyte length to memcpy. The observed result is an out-of-bounds read and process crash; opening the file alone does not trigger the issue because tile decoding is required. This issue is fixed in version 1.23.1.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-62292?


## How do I fix CVE-2026-62292?

Upgrade to a fixed version.

## Is CVE-2026-62292 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62292 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62292 and fix it if it is affected.

What it is: CVE-2026-62292 is a high-severity vulnerability in strukturag libheif, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62292 exists.

Affected product: strukturag libheif. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62292/ (Markdown: https://insights.sbomify.com/CVE-2026-62292/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62292
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62292
- OSV: https://osv.dev/vulnerability/CVE-2026-62292

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62292/
Summaries are generated and may contain mistakes; the official description above is the record.