Advisory

GHSA-j7fr-3v8c-3qc3

Also known as: CVE-2026-54620

Summary

sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-07-28 16:23 UTC
Modified
2026-07-28 16:35 UTC

Affected packages and fixes

sqlite3-ruby

RubyGems · All systems

Affected

  • introduced 2.1.0, fixed 2.9.5 (ecosystem)

Fixed versions

2.9.5

Fix

The export has no generic command for this ecosystem.

sqlite3

RubyGems · All systems

Affected

  • introduced 2.1.0, fixed 2.9.5 (ecosystem)

Fixed versions

2.9.5

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences