vciy

Strukturag libheif, out-of-bounds read: 11 records, one defect family

Strukturag libheif has been reported 11 separate times for the same kind of mistake, CWE-125, between 2025-12-29 and 2026-08-18. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.

What this page is, and what it is not

The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Strukturag libheif and carries CWE-125, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.

One record is an incident. 11 filings, between 2025-12-29 and 2026-08-18, all landing on the same weakness class in the same product, is a habit in what gets reported here, and a habit is something you can plan around. This is what we held on 2026-09-20.

A repeat is evidence about where to look. If you are reviewing Strukturag libheif, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.

What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.

20252026CVE-2025-68431, published 2025-12-29CVE-2026-32738, published 2026-05-19CVE-2026-32882, published 2026-05-19CVE-2026-41069, published 2026-05-22CVE-2026-41071, published 2026-05-22CVE-2026-49271, published 2026-06-19CVE-2026-47251, published 2026-07-21CVE-2026-47254, published 2026-07-21CVE-2026-48029, published 2026-07-22CVE-2026-62291, published 2026-08-18CVE-2026-62292, published 2026-08-18
10 of the 11 were published in 2026, and the rest are spread over 8 months, so this is one concentrated year with a tail rather than a steady rate.

The names the authorities used

One spelling, used by every authority that filed one of these records: strukturag libheif.

These records name more than one weakness class each. All 11 carry CWE-125, which is what this family was grouped on, and 2 of them also name CWE-190, integer overflow or wraparound. The roster below shows what each record names; both readings are the record's own, filed together by the same authority. 3 other classes appear across the family as well.

Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.

What the records offer

No record in this family publishes a fixed version in held sources.

The earliest was published 2025-12-29 and the latest 2026-08-18. That span is how long this product kept producing this weakness, not how long any one record took to fix.

What this page does not cover

This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Everything this vendor has, including records outside this family:

CVE-2025-68431libheif has Potential Heap Buffer Over-ReadCWE-125: Out-of-bounds Read
CVE-2026-32738libheif has a Heap OOB Read/SEGV Crash via Zero samples_per_chunkCWE-125: Out-of-bounds Read
CVE-2026-32882libheif: Heap Buffer OOB Read in overlay compositing due to wrong alpha strideCWE-125: Out-of-bounds Read
CVE-2026-41069libheif allows Out-of-bounds vector access leading to invalid dereference (DoS)CWE-125: Out-of-bounds Read
CVE-2026-41071libheif: Heap buffer over-read in SampleAuxInfoReader via crafted HEIF sequence file with mismatched saiz sample countCWE-125: Out-of-bounds Read
CVE-2026-47251libheif has an incomplete fix for CVE-2026-3949: integer overflow bypass in vvdec_push_data2CWE-125: Out-of-bounds Read
CVE-2026-47254libheif Has Heap Buffer Overflow in `Track::get_next_sample_raw_data()` -- OOB Chunk Vector AccessCWE-125: Out-of-bounds Read
CVE-2026-48029libheif: heap OOB read in ImageItem_Grid::decode_grid_tile via irot-induced tile-coordinate underflowCWE-125: Out-of-bounds Read
CVE-2026-49271libheif: Wrapped icef compressed-unit range check causes out-of-bounds read in uncompressed HEIF decoderCWE-125: Out-of-bounds Read
CVE-2026-62291libheif: Heap out of bounds write in libheif uncompressed encoder when writing images with mismatched auxiliary alpha…CWE-125: Out-of-bounds Read
CVE-2026-62292libheif: Out-of-bounds read in uncompressed unci tile range slicingCWE-125: Out-of-bounds Read

11 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.

Everything on this page is free. Public data. Withholding it protects nothing.