LOW GitHub
CVE-2026-54620
sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks
## Summary
Using `Database#create_aggregate`, `#create_aggregate_handler`, or `Database#define_aggregator` to define an aggregate function, and then using an open statement calling that function after the database has been explicitly closed will result in an invalid memory read and a segmentation fault.
## Mitigation
Upgrade to sqlite3 gem v2.9.5 or later.
As a workaround, avoid using an aggregate function after closing the database.
## Severity
The sqlite3-ruby maintainers assess this as
Affected Products
- rubygems/sqlite3-ruby >= 2.1.0, <= 2.9.4
- rubygems/sqlite3 >= 2.1.0, <= 2.9.4
References
- https://github.com/advisories/GHSA-j7fr-3v8c-3qc3
- https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-j7fr-3v8c-3qc3
- https://github.com/sparklemotion/sqlite3-ruby/pull/711
- https://github.com/sparklemotion/sqlite3-ruby/commit/b24e1e6076528b7f95f99acf7a81c70d0004c
This low severity vulnerability was published on 2026-07-28 via GitHub. Affected: rubygems/sqlite3-ruby >= 2.1.0, <= 2.9.4, rubygems/sqlite3 >= 2.1.0, <= 2.9.4.
vulnfeed aggregates 9166 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.