sqlite3-ruby SQL truncation in string length conversion
sparklemotion sqlite3-ruby
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| sqlite3 RubyGems |
|
|
Original description
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full value before binding it. Exploitation requires the application and server to accept and retain the unusually large attacker-controlled string. If a dropped SQL clause contained a bind placeholder, binding raises SQLite3::RangeException instead of running the query. This issue is fixed in version 2.10.2.
From the CVE record · GitHub_M
References
- github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-4fqr-96q8-xrfx
- github.com/sparklemotion/sqlite3-ruby/pull/762
- github.com/sparklemotion/sqlite3-ruby/commit/41059aa3ccc2c0f910d6df4fccfe36b3c3c6c649
- github.com/sparklemotion/sqlite3-ruby/releases/tag/v2.10.2
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-128084.json
- nvd.nist.gov/vuln/detail/CVE-2026-128084
- github.com/rubysec/ruby-advisory-db/blob/master/gems/sqlite3/GHSA-4fqr-96q8-xrfx.yml
- github.com/sparklemotion/sqlite3-ruby