Quick answers
- Is CVE-2026-41069 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41069 being exploited in the wild.
- How severe is CVE-2026-41069?
- Medium severity, with a CVSS score of 6.5, published 22 May 2026.
- Which products and versions are affected?
- struktur AG Libheif <= 1.21.2.
- Is there a fix for CVE-2026-41069?
- A patch was published on 2026-05-19: Fixed in version 1.22.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41069 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41069?
- Check whether you run struktur AG Libheif at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read and subsequent NULL pointer dereference exists in the SampleAuxInfoReader constructor within libheif/sequences/track.cc. The vulnerability is triggered when a malformed HEIF file contains a specific combination of metadata: a zero entry count in the Sample to Chunk Box (stco) and Sample Auxiliary Information Offsets Box (saio), but a non-zero sample count in the Sample Auxiliary Information Sizes Box (saiz). This configuration causes the parser to enter a loop and attempt to access an empty 'chunks' vector at index 0. An attacker can exploit this by providing a crafted HEIF/AVIF file to any application using the libheif public API (e.g., heif_context_read_from_file). The issue is fixed in version 1.22.0.
Affected products
- strukturag libheif <= 1.21.2
Timeline
- 2026-05-19: patched: Fixed in version 1.22.0
- 2026-05-22: disclosed: CVE-2026-41069 published