Ruby process crash via freed function callback
Published Jul 28, 2026 · Updated Jul 28, 2026
Use-after-free in Sparkle Motion sqlite3-ruby 2.9.4 and earlier allows local users to crash Ruby processes via custom function redefinition. The @functions registry keys Ruby blocks only by function name, so redefining a name replaces the old reference even though SQLite retains arity-specific callback entries. Triggering the invalid read requires local Ruby-code execution, a garbage-collection cycle, and later invocation of the earlier definition; the documented result is a segmentation fault.
Summary
What happened
Use-after-free in Sparkle Motion sqlite3-ruby 2.9.4 and earlier allows local users to crash Ruby processes via custom function redefinition. The @functions registry keys Ruby blocks only by function name, so redefining a name replaces the old reference even though SQLite retains arity-specific callback entries. Triggering the invalid read requires local Ruby-code execution, a garbage-collection cycle, and later invocation of the earlier definition; the documented result is a segmentation fault.
The record
- CVE
- CVE-2026-54619
- Published
- Jul 28, 2026
- Updated
- Jul 28, 2026
- Vendor
- Sparkle Motion
- Product
- sqlite3-ruby
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Jul 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.9.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo