Finding and attribution
Padding an image to a requested size that was larger in one dimension and smaller in another could cause heap buffer overflow during sequence encoding. The path is reachable when x264/x265 encoders process later frames with different sizes from the first frame.
Product: libheif. AI system: Anthropic OSS Scanner (model not specified for this finding). Team / organization: Anthropic and libheif maintainers.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The item-level libheif advisory explicitly attributes discovery to Anthropic's OSS Scanner as ANT-2026-QL0PMTMT. The release notes independently state that all listed security issues were found by the scanner. The Anthropic program sources establish model-based scanning, but no per-case model is identified.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary advisory establishes a publicly disclosed security finding and direct Anthropic OSS Scanner attribution. No CVE had been assigned in the libheif release notes at the checked time; the distinct GHSA is used. No exploitation or zero-day status is asserted.
Remediation status: fix documented. Padding now rejects dimensions below the image or its planes and validates all planes before changes; sequence encoders reject mixed-size frames. Fixed in libheif 1.23.7. This concerns encoding workflows, not ordinary file decoding. The libheif v1.23.7 security release is dated 2026-10-26; deployed patch status is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 26 Oct 2026. AI attribution dated 26 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: other, denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: other, denial of service.
Prerequisites / affected scope: A crafted mixed-size image sequence can cause a heap buffer overflow and crash when an application accepts the sequence and re-encodes it using the affected encoder. No code execution is demonstrated..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Padding now rejects dimensions below the image or its planes and validates all planes before changes; sequence encoders reject mixed-size frames. Fixed in libheif 1.23.7. This concerns encoding workflows, not ordinary file decoding. The libheif v1.23.7 security release is dated 2026-10-26; deployed patch status is not checked.