Quick answers
- Is CVE-2026-41071 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41071 being exploited in the wild.
- How severe is CVE-2026-41071?
- Informational severity, with a CVSS score of 5.1, published 22 May 2026.
- Which products and versions are affected?
- struktur AG Libheif <= 1.21.2.
- Is there a fix for CVE-2026-41071?
- 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-41071 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-41071?
- 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 vulnerability exists in libheif's SampleAuxInfoReader constructor within libheif/sequences/track.cc. The root cause is a lack of validation between the sample count declared in the 'saiz' box and the actual number of chunks available in the track's chunk table. When a crafted HEIF file specifies more samples than chunks, the parsing loop increments the chunk index beyond the bounds of the chunks vector. In release builds where assertions are disabled, this leads to an out-of-bounds read. The vulnerability is triggered during file parsing via heif_context_read_from_file and can result in information disclosure or a denial of service (crash). This 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-19: advisory: GitHub Security Advisory published
- 2026-05-22: disclosed: CVE-2026-41071 published to NVD