Finding and attribution
Opening a file with a moov box used a linear search of stsc entries for every chunk, yielding quadratic work and seconds-to-minutes CPU use on files with many chunks. This issue was also independently reported as GHSA-xf84-wgwm-8vhx; the advisory explicitly says Anthropic OSS Scanner independently discovered the same issue.
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-ZNJZAJWY. 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. The lookup is now a binary search and malformed decreasing first_chunk values are rejected; fixed in libheif 1.23.7. The advisory also discloses OpenAI Codex assistance with the human reporter’s review and drafting; Anthropic discovery attribution is separately explicit. 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: 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: denial of service.
Prerequisites / affected scope: A crafted file can cause excessive CPU work during opening; concurrent requests can exhaust the media worker pool. Applies when untrusted inputs are processed by affected libheif usage..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: The lookup is now a binary search and malformed decreasing first_chunk values are rejected; fixed in libheif 1.23.7. The advisory also discloses OpenAI Codex assistance with the human reporter’s review and drafting; Anthropic discovery attribution is separately explicit. The libheif v1.23.7 security release is dated 2026-10-26; deployed patch status is not checked.