{
  "id": "cve-2026-54619",
  "title": "sqlite3-ruby custom function redefinition use-after-free",
  "product": "sqlite3-ruby",
  "ai_system": "depthfirst AI security agents (specific model not identified for this Ruby research)",
  "organization": "depthfirst / respective project maintainers",
  "summary": "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.",
  "ai_role": "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.",
  "disclosure_date": "2026-07-28",
  "ai_attribution_date": "2026-07-27",
  "classification": "disclosure",
  "classification_note": "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.",
  "cves": [
    "CVE-2026-54619"
  ],
  "source_url": "https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-28hh-pr2h-2w89",
  "ai_source_url": "https://depthfirst.com/research/behind-the-gitlab-rce-a-depthfirst-journey-into-the-ruby-ecosystem",
  "advisory_url": "https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-28hh-pr2h-2w89",
  "remediation": "fix documented",
  "remediation_note": "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.",
  "checked_date": "2026-11-17",
  "impacts": [
    {
      "cves": [
        "CVE-2026-54619"
      ],
      "consequences": [
        "other"
      ],
      "conditions": "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": "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.",
      "source_url": "https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-28hh-pr2h-2w89",
      "checked_date": "2026-11-17"
    }
  ],
  "cvss": [
    {
      "cve": "CVE-2026-54619",
      "version": "4.0",
      "score": 2,
      "vector": "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",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/54xxx/CVE-2026-54619.json",
      "source_name": "CNA CVE Program record",
      "checked_date": "2026-11-17"
    }
  ]
}
