{"apiVersion":"1.0","identifier":"CVE-2026-62377","description":"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.","publishedAt":"2026-08-18T22:17:03","lastModifiedAt":"2026-08-19T19:17:21","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-62377","cvssScore":4.3,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","epssProbability":0.00325,"riskScore":0.44,"affectedProduct":"libheif","affectedVersions":"<=1.23.0","vulnerabilityType":"Library","operatingSystems":[],"links":{"self":"https://www.redsauce.net/api/cves/CVE-2026-62377","webPages":{"es":"https://www.redsauce.net/es/cves/CVE-2026-62377","en":"https://www.redsauce.net/en/cves/CVE-2026-62377","fr":"https://www.redsauce.net/fr/cves/CVE-2026-62377","pt":"https://www.redsauce.net/pt/cves/CVE-2026-62377","de":"https://www.redsauce.net/de/cves/CVE-2026-62377","sk":"https://www.redsauce.net/sk/cves/CVE-2026-62377","el":"https://www.redsauce.net/el/cves/CVE-2026-62377"},"source":"https://nvd.nist.gov/vuln/detail/CVE-2026-62377"}}