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.
Published: 2026-11-13
Score: 4.8 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-4fqr-96q8-xrfx sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger
History

Fri, 13 Nov 2026 22:15:00 +0000

Type Values Removed Values Added
First Time appeared Sparklemotion
Sparklemotion sqlite3-ruby
Vendors & Products Sparklemotion
Sparklemotion sqlite3-ruby

Fri, 13 Nov 2026 19:00:00 +0000

Type Values Removed Values Added
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.
Title sqlite3-ruby: SQL Query Truncation
Weaknesses CWE-681
References
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

Sparklemotion Sqlite3-ruby
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-13T18:47:22.594Z

Reserved: 2026-11-12T21:24:51.130Z

Link: CVE-2026-128084

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-13T19:19:31.050

Modified: 2026-11-13T19:19:31.050

Link: CVE-2026-128084

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-13T22:00:09Z

Weaknesses