Finding and attribution
The bundled PCRE regular-expression engine can write one byte past a heap buffer for a crafted revspec.
Product: libgit2. AI system: Claude Mythos Preview. Team / organization: Anthropic.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): Anthropic CVD item explicitly attributes discovery to Claude Mythos Preview; the libgit2 advisory identifies the matching issue.
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: Public disclosure is documented. Sources do not establish exploitation in the wild or zero-day status. CVD finding is static-analysis-only; no CVE confirmed.
Remediation status: not established. The advisory lists no patched libgit2 version. It describes a structural fix in PCRE2 that was not backported to bundled PCRE 8.x.
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 18 Jul 2026. AI attribution dated 17 Aug 2026. Sources checked 15 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: With libgit2’s default built-in PCRE backend, a specially structured `:/pattern` revspec can cause a deterministic one-byte heap out-of-bounds write in PCRE. Any consumer passing attacker-influenced strings to revspec is exposed; no downstream consequence is established..
Exploitation evidence: The advisory confirms a deterministic reachable trigger; it does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The advisory lists no patched libgit2 version. It describes a structural fix in PCRE2 that was not backported to bundled PCRE 8.x.