NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · RubyGems

CVE-2026-54620: sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks

lowCVSS 4.0 2.0GHSA-j7fr-3v8c-3qc3

Summary Using Database#createaggregate, #createaggregatehandler, or Database#defineaggregator 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.

Published Jul 28, 2026

Affected packages

sqlite3-ruby

Ecosystem
RubyGems
Affected
>= 2.1.0, <= 2.9.4
Fixed in
2.9.5
Check
bundle info sqlite3-ruby

sqlite3

Ecosystem
RubyGems
Affected
>= 2.1.0, <= 2.9.4
Fixed in
2.9.5
Check
bundle info sqlite3

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to cla7aye15I4nd.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More RubyGems vulnerabilities

All RubyGems entries