Finding and attribution
The Revelio paper identifies a out-of-bounds read in The Sleuth Kit v4.15.0: index update-sequence array out-of-bounds read. It lists the author-assessed severity as Moderate 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 19 of the seven-project real-world hunt.
Product: The Sleuth Kit v4.15.0. 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: Not established in the cited evidence.
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: not established. The paper marked maintainer response pending at publication; no public issue identifier, advisory, or fix was established.
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 20 Jun 2026. AI attribution dated 20 Jun 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.
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: Paper identifies an out-of-bounds read in the index update-sequence array; whether data is exposed is not established..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The paper marked maintainer response pending at publication; no public issue identifier, advisory, or fix was established.