Skip to main content
VulnerabilityPublished

CVE-2026-62377: strukturag libheif · Reachable Assertion

Affects strukturag libheifSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.23.1 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.23.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade strukturag libheif to 1.23.1.

Affected software

ProductAffectedFixed in
strukturaglibheifAffected
  • <1.23.1
Fixed in
  • 1.23.1
GitHubstrukturag/libheifpkg:github/strukturag/libheifOther threatsAffected
  • <=1.23.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade libheif to version 1.23.1 or later, where this issue is fixed. Until then, avoid processing untrusted HEIF files with vulnerable versions. No other mitigations are specified or required.

Description

A reachable assertion vulnerability exists in libheif versions 1.23.0 and earlier. When processing crafted HEIF sequences via heif_context_read_from_memory(), the context may end up with no registered sequence tracks, causing a crash when heif_context_get_track(ctx, 0) is called. This occurs because an assertion in get_track() aborts in debug builds, while release builds dereference an empty map leading to undefined behavior and typical crashes. The issue is fixed in version 1.23.1.

References

Community reviews

Loading reviews…