PT-2026-65657 · Rubygems · Sqlite3+1

Published 2026-07-28 · Updated 2026-07-28

OSV

CVSS v4.0

2.0

Low

Base vector

AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

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.

Exploit

Fix

Use After Free

Weakness Enumeration

CWE-416

Related Identifiers

GHSA-J7FR-3V8C-3QC3

Affected Products

Sqlite3

Sqlite3-Ruby

References · 8

• 🔥 https://github.com/rubysec/ruby-advisory-db/blob/master/gems/sqlite3/CVE-2026-54620.yml · Exploit
• https://cve.org/CVERecord/SearchResults?query=CVE-2026-54620 · Security Note
• https://osv.dev/vulnerability/GHSA-j7fr-3v8c-3qc3 · Vendor Advisory
• https://github.com/sparklemotion/sqlite3-ruby/releases/tag/v2.9.5 · Note
• https://github.com/sparklemotion/sqlite3-ruby/pull/711 · Note
• https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-j7fr-3v8c-3qc3 · Note
• https://github.com/sparklemotion/sqlite3-ruby · Note
• https://github.com/sparklemotion/sqlite3-ruby/commit/b24e1e6076528b7f95f99acf7a81c70d0004c726 · Note