GHSA-j7fr-3v8c-3qc3
sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| RubyGems | sqlite3-ruby | >= 2.1.0, < 2.9.5 | 2.9.5 |
| RubyGems | sqlite3 | >= 2.1.0, < 2.9.5 | 2.9.5 |
Details
As written in the advisory (Markdown source, shown as plain text).
## 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 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.
References
External links from the advisory. They lead to third-party sites.
- 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/b24e1e6076528b7f95f99acf7a81c70d0004c726
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/sqlite3/CVE-2026-54620.yml
- https://github.com/sparklemotion/sqlite3-ruby
- https://github.com/sparklemotion/sqlite3-ruby/releases/tag/v2.9.5
- https://www.cve.org/CVERecord/SearchResults?query=CVE-2026-54620