VulnerabilityPublished 13 Nov 2026

CVE-2026-128084: sparklemotion sqlite3-ruby · Incorrect Conversion Between Numeric Types

Affects sparklemotion sqlite3-rubySource CVE Database V5

Compare

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

Data as of 13 Nov 2026, 19:04 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 sparklemotion sqlite3-ruby to 2.10.2.

Affected software

Product	Affected	Fixed in
sparklemotionsqlite3-ruby	Affected <2.10.2	Fixed in 2.10.2

AI-suggested

Upgrade sqlite3-ruby to version 2.10.2 or later, where this issue is fixed. No other mitigation is necessary as the fix addresses the root cause.

Description

A numeric type conversion flaw in sqlite3-ruby prior to version 2.10.2 causes string lengths to be cast to int on 64-bit platforms. This can truncate SQL strings or bound values larger than 4 GiB, potentially dropping trailing SQL clauses such as WHERE conditions. If a dropped clause contained a bind placeholder, an exception is raised instead of executing the query. The issue is fixed in version 2.10.2.

Impact

An attacker able to supply extremely large SQL strings or bound parameters may cause truncation of SQL queries, potentially bypassing conditions like WHERE clauses. This can lead to altered query logic with limited impact on confidentiality and integrity, as indicated by the CVSS vector (low confidentiality and integrity impact, no availability impact). However, exploitation is constrained by the need for very large inputs and application acceptance of such data.

Summary

The sqlite3-ruby library, which provides Ruby bindings for SQLite3, improperly casts Ruby string lengths to a 32-bit int before passing SQL statements and bound parameters to SQLite. On 64-bit systems, strings of 4 GiB or larger wrap around, causing SQLite to process only a truncated prefix of the SQL or bound data. This truncation can lead to dropped SQL clauses, such as WHERE conditions, potentially altering query behavior. If a dropped clause includes a bind placeholder, SQLite3::RangeException is raised, preventing query execution. Exploitation requires the application and server to accept and retain very large attacker-controlled strings. The vulnerability is resolved in sqlite3-ruby version 2.10.2.

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, 19:04 UTC

WeaknessesCWE-681

Technical details

References

Community reviews

Related threats