AI Science Tracker

sqlite3-ruby custom function redefinition use-after-free

sqlite3-ruby · AI involvement attributed to depthfirst AI security agents (specific model not identified for this Ruby research)

Finding and attribution

When SQLite functions are redefined under the same name with a different arity or text encoding, sqlite3-ruby can replace its retained Ruby block reference while SQLite still retains the earlier registration, permitting garbage collection followed by an invalid read and process segmentation fault.

Product: sqlite3-ruby. AI system: depthfirst AI security agents (specific model not identified for this Ruby research). Team / organization: depthfirst / respective project maintainers.

CVE identifiers: CVE-2026-54619.

AI and human contribution (source account): depthfirst’s primary July 27, 2026 Ruby ecosystem report identifies CVE-2026-54619 as an issue uncovered in the research, and says its AI security agents analyzed the projects and validated each finding with a triggering input, reproduction script and evidence such as ASan output before manual review. The issue-specific section describes this exact vulnerability. The affected project maintainer advisory validates the vulnerability and fix. No specific model or per-case human/agent split is 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 maintainer advisory and CNA record provide public dates for CVE-2026-54619; the depthfirst account is dated 2026-07-27. The sources do not report exploitation in the wild or establish zero-day status.

Remediation status: fix documented. sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5. This documents upstream package version guidance and does not establish downstream distribution patch state.

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 28 Jul 2026. AI attribution dated 27 Jul 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Low · highest recorded score 2. 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-54619: CVSS 4.0 · 2 (Low) · CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. CNA CVE Program record · checked 17 Nov 2026.

CVE-2026-54619: other.
Prerequisites / affected scope: Application code defines the same SQLite function name with different arity or encoding; garbage collection may occur before SQLite invokes the earlier retained function..
Exploitation evidence: The maintainers say invalid memory read and segmentation fault are reliably triggered with particular code structure after GC, but no general denial-of-service exploit is known.. Impact source · checked 17 Nov 2026.

Documented fix: sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5. This documents upstream package version guidance and does not establish downstream distribution patch state.

Original evidence

Download this source record (JSON)

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