CVE-2026-54619
Received Received - Intake

Use-After-Free in sqlite3 Ruby Gem

Vulnerability report for CVE-2026-54619, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-28

Last updated on: 2026-07-28

Assigner: GitHub, Inc.

Description

sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, 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
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
sparklemotion sqlite3-ruby to 2.9.5 (exc)
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 vulnerability is a use-after-free issue in the sqlite3-ruby gem (versions 2.9.4 and earlier). It occurs when a SQLite function is redefined with a different number of arguments or text encoding. The original function handler is freed while SQLite may still reference it, leading to memory corruption and potential crashes.

Detection Guidance

This vulnerability is specific to the sqlite3-ruby gem (versions <= 2.9.4). To detect it, check your gem version with: gem list sqlite3. If the version is 2.9.4 or lower, the system is vulnerable. No network detection is required as this is a local code execution issue.

Impact Analysis

This vulnerability can cause invalid memory reads, segmentation faults, or crashes in applications using the sqlite3-ruby gem. It may lead to unexpected behavior or denial-of-service conditions under specific code structures, particularly after garbage collection.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. The issue is a use-after-free flaw in the sqlite3-ruby gem that could cause crashes or memory corruption but does not involve data breaches or unauthorized access. Compliance impacts would only occur if exploitation led to system instability affecting data integrity or availability.

Mitigation Strategies

Upgrade the sqlite3-ruby gem to version 2.9.5 or later using: gem install sqlite3 -v '>=2.9.5'. Alternatively, avoid defining custom SQLite functions with the same name but different arity or text encodings in your code.

Chat Assistant

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

EPSS Chart