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.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-28hh-pr2h-2w89 | sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 29 Jul 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sparklemotion
Sparklemotion sqlite3-ruby |
|
| Vendors & Products |
Sparklemotion
Sparklemotion sqlite3-ruby |
Tue, 28 Jul 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 28 Jul 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity | |
| Weaknesses | CWE-416 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-28T19:33:33.444Z
Reserved: 2026-06-15T20:07:02.184Z
Link: CVE-2026-54619
Updated: 2026-07-28T19:33:30.338Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-29T15:10:45Z
Weaknesses
Github GHSA