AI Science Tracker

OpenEXR Python RGB channel coalescing heap buffer overflow

OpenEXR · AI involvement attributed to Claude

Finding and attribution

With default separate_channels=false, distinct RGB channel groups can coalesce to one Python binding key but have different component counts. The array is allocated for three components and a later four-component frame-buffer slice writes approximately 33% past the end when processing an untrusted OpenEXR file.

Product: OpenEXR. AI system: Claude. Team / organization: Anthropic.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The OpenEXR maintainer advisory states that Anthropic found this issue using Claude and that Ada Logics validated it. This supports case-specific AI-assisted discovery with independent human validation; the source does not specify Claude’s individual investigative steps or model version.

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 advisory documents the public disclosure and fix but does not establish whether defenders knew of the issue or whether it was exploited before disclosure.

Remediation status: fix documented. The OpenEXR GHSA lists fixed release versions 3.3.15, 3.4.17, and 3.5.3. This records the upstream fix only; downstream packaging/deployment is not inferred.

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 31 Oct 2026. AI attribution dated 31 Oct 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: other.

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.
Prerequisites / affected scope: A Python program must call OpenEXR.File with default arguments on an untrusted file. The advisory does not establish controlled code execution..
Exploitation evidence: The advisory describes a file-crafted reproducer/attack condition; it does not report observed exploitation.. Impact source · checked 16 Nov 2026.

Documented fix: The OpenEXR GHSA lists fixed release versions 3.3.15, 3.4.17, and 3.5.3. This records the upstream fix only; downstream packaging/deployment is not inferred.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases