CVE-2026-62377

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-18 22:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-22 16:09 UTC Last updatedMost recent change to the record

Details

Published

2026-08-18 22:17 UTC

Last modified

2026-10-22 16:09 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-617

Record status

Deferred

Attack profile CVSS 3.1 · 4.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low