{"id":"CVE-2026-54619","aliases":["DEBIAN-CVE-2026-54619","EUVD-2026-49896","GHSA-28hh-pr2h-2w89","UBUNTU-CVE-2026-54619"],"status":"published","title":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","description":"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.","severity":{"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","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00142,"percentile":0.03543,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-416"],"published":"2026-07-28T16:21:20Z","modified":"2026-10-28T11:14:44Z","fixes":[{"ecosystem":"RubyGems","package":"sqlite3-ruby","fixed_in":["2.9.5"],"sources":["ghsa","osv"]},{"ecosystem":"RubyGems","package":"sqlite3","fixed_in":["2.9.5"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"ruby-sqlite3","fixed_in":["2.9.5-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"RubyGems","package":"sqlite3-ruby","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.9.4"},{"fixed":"2.9.5"}]}]},{"source":"ghsa","ecosystem":"RubyGems","package":"sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.9.4"},{"fixed":"2.9.5"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4.2-4","1.6.9-1","1.6.9-2","1.7.3-1","1.7.3-2","2.10.0-1~exp1","2.9.0-1","2.9.1-1","2.9.3-1","2.9.5-1","2.9.5-2","2.9.6-1","2.9.6-2"]},{"source":"osv","ecosystem":"Debian:13","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.7.3-1","1.7.3-2","2.10.0-1~exp1","2.9.0-1","2.9.1-1","2.9.3-1","2.9.5-1","2.9.5-2","2.9.6-1","2.9.6-2"]},{"source":"osv","ecosystem":"Debian:14","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.5-1"}]}],"versions":["1.7.3-1","1.7.3-2","2.9.0-1","2.9.1-1","2.9.3-1"]},{"source":"osv","ecosystem":"RubyGems","package":"sqlite3-ruby","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.5"}]}],"versions":["0.5.0","0.6.0","0.9.0","1.0.0","1.0.1","1.1.0","1.2.0","1.2.1","1.2.2","1.2.3","1.2.4","1.2.5","1.3.0","1.3.0.beta.1","1.3.0.beta.2","1.3.1","1.3.2","1.3.3","1.3.3.beta.1"]},{"source":"osv","ecosystem":"RubyGems","package":"sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.5"}]}],"versions":["0.0.0","0.0.1","0.0.2","0.0.3","0.0.4","0.0.5","0.0.6","0.0.7","0.0.8","0.1.0","0.1.1","1.3.10","1.3.11","1.3.12","1.3.13","1.3.3","1.3.3.beta.1","1.3.4","1.3.5","1.3.6","1.3.7","1.3.8","1.3.9","1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.5.0","1.5.0.rc1","1.5.0.rc2","1.5.1","1.5.2","1.5.3","1.5.4","1.6.0","1.6.0.rc1","1.6.0.rc2","1.6.1","1.6.2","1.6.3","1.6.4","1.6.5","1.6.5.rc1","1.6.6","1.6.7","1.6.8","1.6.9","1.7.0","1.7.1","1.7.2","1.7.3","2.0.0","2.0.1","2.0.2","2.0.3","2.0.4","2.1.0","2.1.0.rc1","2.1.0.rc2","2.1.0.rc3","2.1.1","2.2.0","2.3.0","2.3.1","2.4.0","2.4.1","2.5.0","2.5.0.rc1","2.6.0","2.7.0","2.7.1","2.7.2","2.7.3","2.7.4","2.8.0","2.8.1","2.9.0","2.9.1","2.9.2","2.9.2.rc2","2.9.3","2.9.4"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.3.10-1","1.3.11-1","1.3.11-1build1","1.3.11-2","1.3.11-2build1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.3.13-1","1.3.13-1build1","1.3.13-1build2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.3.13-1build2","1.4.2-2build1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4.2-3","1.4.2-3build1","1.4.2-4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4.2-4build2","1.4.2-4build3","1.4.2-4build4"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.7.3-2","2.9.5-2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"ruby-sqlite3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.7.3-1","1.7.3-2"]}],"products":[{"vendor":"sparklemotion","product":"sqlite3-ruby"}],"references":[{"url":"https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-28hh-pr2h-2w89","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/sparklemotion/sqlite3-ruby/pull/710","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/sparklemotion/sqlite3-ruby/commit/2bd436d17f77cdd4c31b00fe9d50b0d21cbaf033","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/sparklemotion/sqlite3-ruby/releases/tag/v2.9.5","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/sqlite3/CVE-2026-54619.yml","tags":["web"]},{"url":"https://www.cve.org/CVERecord/SearchResults?query=CVE-2026-54619","tags":["web"]},{"url":"https://github.com/advisories/GHSA-28hh-pr2h-2w89"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54619.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-54619","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-54619","tags":["advisory"]},{"url":"https://github.com/sparklemotion/sqlite3-ruby","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-54619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-54619","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-54619","title":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","description":"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.","status":"published","published":"2026-07-28T16:21:20.943Z","modified":"2026-07-28T19:33:33.444Z","cvss":[{"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","level":"low","assessor":"cna"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T13:38:09.774038Z"}],"euvd":[{"id":"EUVD-2026-49896","description":"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.","status":"published","published":"2026-07-28T16:21:20Z","modified":"2026-07-28T19:33:33Z","cvss":[{"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","level":"low"}],"updated_at":"2026-11-02T18:02:30.59681Z"}],"ghsa":[{"id":"GHSA-28hh-pr2h-2w89","title":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","description":"## Summary\n\nUsing `Database#create_function` or `Database#define_function` to define the same function name more than once with different numbers of arguments (\"arity\") or text encodings will result in a invalid memory read and a segmentation fault.\n\n## Mitigation\n\nUpgrade to sqlite3 gem v2.9.5 or later.\n\nAs a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding).\n\n## Severity\n\nThe sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.","status":"published","published":"2026-07-28T16:21:31Z","modified":"2026-07-28T16:21:33Z","cvss":[{"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","level":"low"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T14:40:53.707378Z"}],"nvd":[{"id":"CVE-2026-54619","description":"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.","status":"published","published":"2026-07-28T17:16:52.65Z","modified":"2026-10-23T23:10:00.157Z","cvss":[{"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"low","assessor":"secondary"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T14:12:33.249634Z"}],"osv":[{"id":"CVE-2026-54619","title":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","description":"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.","status":"published","published":"2026-07-28T16:21:20.943Z","modified":"2026-10-28T11:14:44.27319878Z","cvss":[{"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","level":"low"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T15:45:10.818486Z"},{"id":"DEBIAN-CVE-2026-54619","description":"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.","status":"published","published":"2026-07-28T17:16:52.65Z","modified":"2026-10-24T10:01:05.689218495Z","cvss":[{"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"low"}],"updated_at":"2026-11-02T15:45:57.236551Z"},{"id":"GHSA-28hh-pr2h-2w89","title":"sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity","description":"## Summary\n\nUsing `Database#create_function` or `Database#define_function` to define the same function name more than once with different numbers of arguments (\"arity\") or text encodings will result in a invalid memory read and a segmentation fault.\n\n## Mitigation\n\nUpgrade to sqlite3 gem v2.9.5 or later.\n\nAs a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding).\n\n## Severity\n\nThe sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.","status":"published","published":"2026-07-28T16:21:31Z","modified":"2026-07-28T16:35:58.822345Z","cvss":[{"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","level":"low"}],"cwes":["CWE-416"],"updated_at":"2026-11-02T15:46:33.956911Z"},{"id":"UBUNTU-CVE-2026-54619","description":"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.","status":"published","published":"2026-07-28T17:16:00Z","modified":"2026-10-17T12:59:06.4878585Z","cvss":[{"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","level":"low"}],"updated_at":"2026-11-02T16:56:41.382716Z"}]}}