Finding and attribution
The Revelio paper identifies a out-of-bounds read in OpenEXR v3.4.10: manifest string prefix out-of-bounds read. It lists the author-assessed severity as Critical and says the finding was manually validated with a reproducible sanitizer-backed proof of vulnerability through a reachable project test harness. This is Table V item 3 of the seven-project real-world hunt.
Product: OpenEXR v3.4.10. AI system: Revelio using Claude Haiku 4.5 and Claude Sonnet 4.6. Team / organization: UC Berkeley Revelio research team and affected project maintainers.
CVE identifiers: CVE-2026-42216.
AI and human contribution (source account): The paper describes Revelio as using Claude Haiku 4.5 for hypothesis generation and Claude Sonnet 4.6 for proof-of-vulnerability confirmation; its experimental-method section says this configuration was used for the seven-project OSS-Fuzz hunt. The authors state all 19 tabled findings were manually validated and sanitizer-confirmed. The paper does not provide a per-item model trajectory, so the exact division of Claude work within this row is not independently stated.
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 paper publicly identifies this distinct finding on 2026-06-20. The authors describe the hunt as searching for previously unknown flaws, but this record does not assert exploitation in the wild or operational zero-day status.
Remediation status: fix documented. The OpenEXR advisory confirms the unchecked IDManifest prefix read and lists patched releases 3.2.9, 3.3.11, and 3.4.11.
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 5 May 2026. AI attribution dated 20 Jun 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.8. 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.
- CVE-2026-42216: CVSS 4.0 · 8.8 (High) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-42216: CVSS 3.1 · 8.1 (High) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H. redhat-SADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2026-42216: other.
Prerequisites / affected scope: If the previous string is longer than 255 bytes, the next string is expected to begin with a 2-byte prefix length..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The OpenEXR advisory confirms the unchecked IDManifest prefix read and lists patched releases 3.2.9, 3.3.11, and 3.4.11.