{"answers":{"affected":"4 open source packages ship an affected version, including sqlite3-ruby and sqlite3.","exploited":"There is no known exploitation of CVE-2026-54620 in the wild and no public exploit code.","fix":"Upgrade sqlite3-ruby to 2.9.5 or later.","what":"CVE-2026-54620 is a low-severity use after free vulnerability in sparklemotion sqlite3-ruby, published on 28 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54620 and fix it if it is affected.\n\nWhat it is: CVE-2026-54620 is a low-severity use after free vulnerability in sparklemotion sqlite3-ruby, published on 28 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54620 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sqlite3-ruby (RubyGems): affected from 2.1.0; fixed in 2.9.5\n- sqlite3-ruby (RubyGems): affected from 2.1.0; fixed in 2.9.5\n- sqlite3 (RubyGems): affected from 2.1.0; fixed in 2.9.5\n- sqlite3 (RubyGems): affected from 2.1.0; fixed in 2.9.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54620/ (Markdown: https://insights.sbomify.com/CVE-2026-54620/index.md)","id":"CVE-2026-54620","markdown":"https://insights.sbomify.com/CVE-2026-54620/index.md","name":"CVE-2026-54620","record":{"aliases":["DEBIAN-CVE-2026-54620","GHSA-j7fr-3v8c-3qc3","UBUNTU-CVE-2026-54620"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby SQLite3 bindings","requires_auth":"low_privilege","summary":"An attacker can trigger a use-after-free in SQLite aggregate function callbacks, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks","id":"CVE-2026-54620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"`datamodel-code-generator` vulnerable to code injection via unescaped carriage return in GraphQL Union description","id":"CVE-2026-54621"},"packages":[{"ecosystem":"RubyGems","fixed":["2.9.5"],"introduced":["2.1.0"],"last_affected":[],"package":"sqlite3","purl":null,"source":"GHSA-j7fr-3v8c-3qc3"},{"ecosystem":"RubyGems","fixed":["2.9.5"],"introduced":["2.1.0"],"last_affected":[],"package":"sqlite3","purl":"pkg:gem/sqlite3","source":"GHSA-j7fr-3v8c-3qc3"},{"ecosystem":"RubyGems","fixed":["2.9.5"],"introduced":["2.1.0"],"last_affected":[],"package":"sqlite3-ruby","purl":null,"source":"GHSA-j7fr-3v8c-3qc3"},{"ecosystem":"RubyGems","fixed":["2.9.5"],"introduced":["2.1.0"],"last_affected":[],"package":"sqlite3-ruby","purl":"pkg:gem/sqlite3-ruby","source":"GHSA-j7fr-3v8c-3qc3"}],"prev":{"headline":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","id":"CVE-2026-54619"},"products":["sqlite3-ruby"],"published":"2026-07-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["sparklemotion"]},"summary":"An attacker can trigger a use-after-free in SQLite aggregate function callbacks, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-54620/"}