CVE-2026-62377
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 25% of all known CVEs.
References
Related Vulnerabilities
Other CWE-617 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-8617 | High | 7.5 | 93% | - | Fix |
| CVE-2020-36222 | High | 7.5 | 78% | - | Fix |
| CVE-2006-5779 | High | 7.5 | 76% | - | Fix |
| CVE-2021-27212 | High | 7.5 | 64% | - | Fix |
| CVE-2018-5740 | High | 7.5 | 60% | - | Fix |
| CVE-2023-28425 | Medium | 5.5 | 55% | - | Fix |
Common questions
How do I fix CVE-2026-62377?
Upgrade libheif on debian unstable to 1.23.1-1 or later.
Is CVE-2026-62377 being actively exploited?
Not that we know of. CVE-2026-62377 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.33% is the estimated probability that it will be exploited in the next 30 days. That is higher than 25% of all scored CVEs.
How severe is CVE-2026-62377?
CVE-2026-62377 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-62377 affect?
Published advisories record a fix for libheif (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-62377
Markdown
[](https://tridentstack.com/cve/CVE-2026-62377)HTML
<a href="https://tridentstack.com/cve/CVE-2026-62377"><img src="https://tridentstack.com/cve/badge/CVE-2026-62377.svg" alt="CVE-2026-62377"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.