CVE-2026-54620
Received Received - Intake

SQLite3 Ruby Bindings Use-After-Free in Aggregate Functions

Publication date: 2026-07-28

Last updated on: 2026-07-28

Assigner: GitHub, Inc.

Description
sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-28
Last Modified
2026-07-28
Generated
2026-07-28
AI Q&A
2026-07-28
EPSS Evaluated
N/A
NVD
CVE-2026-54620
EUVD
EUVD-2026-49899

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
sparklemotion sqlite3-ruby From 2.1.0 (inc) to 2.9.4 (inc)
sparklemotion sqlite3-ruby 2.9.5
sqlite sqlite3 2.9.5

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the sqlite3-ruby gem affecting versions 2.1.0 to 2.9.4. It occurs when aggregate functions are defined and then used via an open statement after the database has been closed. This leads to accessing freed memory, causing potential crashes or memory corruption.

Detection Guidance

This vulnerability affects the sqlite3-ruby gem versions 2.1.0 to 2.9.4. To detect it, check the installed version of the sqlite3 gem using the command gem list sqlite3. If the version is between 2.1.0 and 2.9.4, the system is vulnerable.

Impact Analysis

The vulnerability can cause application crashes due to segmentation faults when aggregate functions are used after database closure. It may also lead to memory corruption if the freed memory is reallocated, though no known general exploits for denial-of-service attacks exist.

Compliance Impact

This vulnerability does not directly impact compliance with GDPR or HIPAA. It is a low-severity use-after-free issue in the sqlite3-ruby gem that could cause segmentation faults under specific conditions but does not involve data breaches or unauthorized access.

Mitigation Strategies

Upgrade the sqlite3 gem to version 2.9.5 or later using the command gem install sqlite3 -v 2.9.5. As a temporary workaround, avoid using aggregate functions after closing the database.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54620. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart