CVE-2026-62377
libheif is a HEIF and AVIF file format decoder and encoder. In …
libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.0 and earlier, a crafted HEIF sequence accepted by heif_context_read_from_memory() can leave the context with no registered sequence tracks and crash when heif_context_get_track(ctx, 0) is called. HeifContext::get_track() in libheif/context.cc executes assert(has_sequence()) before its normal error handling, so assert-enabled builds abort instead of allowing the public wrapper in libheif/api/libheif/heif_sequences.cc to return null. In release builds, removing the assertion lets the track_id zero path dereference m_tracks.begin()->second on an empty map, which is undefined behavior and typically crashes. The issue is reachable through documented public APIs after parsing attacker-controlled bytes. This issue is fixed in version 1.23.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/strukturag/libheif/commit/e1a0bc1c1ae74f8075eaca30a1cdb2b9bee698d3
- github.com/strukturag/libheif/issues/1844
- github.com/strukturag/libheif/releases/tag/v1.23.1
- github.com/strukturag/libheif/security/advisories/GHSA-9ww4-9v47-m7pj
- nvd.nist.gov/vuln/detail/CVE-2026-62377
- cve.org/CVERecord?id=CVE-2026-62377
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.