Loading vulnerability…
CVE-2026-62377 is a reachable assertion and empty-container handling flaw in libheif 1.23.0 and earlier. A crafted HEIF sequence processed through the public memory-parsing API can leave a HeifContext with no registered sequence tracks. A subsequent request for track zero invokes HeifContext::get_track(), which asserts that a sequence exists before normal error handling. Assertion-enabled builds abort; builds without assertions can dereference the first element of an empty track map, resulting in undefined behavior and typically a crash. The issue is fixed in libheif 1.23.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A reachable assertion failure in libheif's HeifContext::get_track() that can abort processing of a valid but empty HEIF sequence file.
A specific vulnerability tracked as CVE-2026-62377 affecting libheif packages on supported Ubuntu LTS and Debian Linux releases, with availability impact indicated by the CVSS vectors.
A specific libheif vulnerability included in AISLE's public registry growth summary.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.