VulnerabilityPublished 13 Nov 2026

CVE-2026-128084: sqlite3-ruby · Possible SQL query truncation when a string is 4 GiB or larger

Affects sqlite3Source GCVE Database

Compare

Authoritative record:CVE-2026-128084· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.10.2 when convenient.

Data as of 13 Nov 2026, 20:19 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	4.8

Patch: Available – fixed in 2.10.2

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade sqlite3 to 2.10.2.

Affected software

Product	Affected	Fixed in
RubyGemssqlite3	Affected <2.10.2	Fixed in 2.10.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade sqlite3-ruby to version 2.10.2 or later, which raises a RangeError for strings longer than INT_MAX bytes and prevents truncation. For earlier versions, reject SQL strings and bound values of 4 GiB or larger before passing them to sqlite3-ruby. Additionally, limit request body sizes well below 4 GiB to prevent exploitation.

Description

The sqlite3-ruby library improperly casts Ruby string lengths from long to int before passing them to SQLite, causing string lengths of 4 GiB or larger to wrap on 64-bit platforms. This results in SQL query truncation where only the first length mod 2^32 bytes are processed. An attacker controlling the SQL string length could truncate queries, potentially dropping trailing clauses such as WHERE. The issue affects SQL strings passed to Database#prepare, #execute, bound parameters, and Ruby-defined SQL functions and aggregates. The vulnerability is fixed in sqlite3-ruby version 2.10.2, which raises a RangeError for strings longer than INT_MAX bytes.

Impact

An attacker able to supply a SQL string or bound value of 4 GiB or larger can cause truncation of the SQL query or bound parameters. This truncation may drop trailing clauses such as WHERE, potentially altering query behavior and bypassing intended filtering or logic. Bound value truncation results in only a prefix of the attacker's input being used, which is less severe if the application validates the full value before binding. Exploitation requires very large input sizes, which are often rejected by application or server limits. No known exploits in the wild have been reported.

CWE-681Incorrect Conversion between Numeric Types (opens in a new tab)
Base weaknessLikelihood of exploit: High
When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur.
Implementation
Avoid making conversion between numeric types. Always check for the allowed ranges.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 20:19 UTC

WeaknessesCWE-681

Technical details

References

Community reviews

Related threats