Finding and attribution
The team reports an AI-agent finding in development code that maintainers corrected on the reporting day. Project Zero states that the defect never reached an official SQLite release, so released users were not affected.
Product: SQLite. AI system: Big Sleep. Team / organization: Google Project Zero and Google DeepMind.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): Big Sleep performed variant analysis with a starting point selected by researchers. Human researchers verified and reported the finding.
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: Previously unknown does not automatically mean an exploited production zero-day. This case was fixed before an official release; no CVE is asserted here.
Remediation status: fix documented. Project Zero reports a same-day upstream correction in early October 2024, before an official release; this record does not invent a precise reporting day.
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 1 Nov 2024. AI attribution dated 1 Nov 2024. Sources checked 13 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 ROWID constraint can trigger a negative-index stack write in release builds; debug assertions stop it, and exploitability is described as likely rather than demonstrated..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Project Zero reports a same-day upstream correction in early October 2024, before an official release; this record does not invent a precise reporting day.