CVE-2026-128084 — Sqlite3 — CWE-681
CVE-2026-128084 is a MEDIUM severity security vulnerability (CWE-681) (CVSS 4.8/10 (EPSS: 0.3%)) affecting Sqlite3. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), allowing unauthorized disclosure of sensitive data (C:H).
📄 Official NVD / MITRE Original Record Text
### Summary sqlite3-ruby cast Ruby string lengths (`long`) to `int` before passing them to SQLite. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger had its length wrap, so SQLite saw only the first `length mod 2^32` bytes. An attacker who controls the length of a SQL string could truncate the query, for example dropping a trailing `WHERE` clause. The affected paths are: - the SQL passed to `Database#prepare`, `#execute`, and related methods - String and Blob values passed to `Statement#bind_param` and related methods - String and Blob values returned from SQL functions and aggregates defined in Ruby (`Database#create_function`, `#create_aggregate`, and related methods) sqlite3 v2.10.2 raises `RangeError` when any of these strings is longer than `INT_MAX` bytes. ### Severity The sqlite3-ruby maintainers have evaluated this as medium severity (CVSS 4.8). Exploitation requires an attacker to get at least 4 GiB into a single SQL string or bound value. Most deployments reject a request body that large before the application sees it, and the server must hold several copies of the string in memory. A truncated bound value is only a prefix of the attacker's input, so the bind paths matter only where the application validated the full value. A truncated SQL string is more serious: when the attacker's input is inlined into the SQL, the clauses that follow it are dropped. If a dropped clause contained a bind placeholder, binding raises `SQLite3::RangeException` instea
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-128084
CVSS 4.8/10 · MEDIUM · 13.11.2026
CWE: CWE-681
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
SQL Injection (SQLi)
Summary: ### Summary
sqlite3-ruby cast Ruby string lengths (long) to int before passing them to SQLite. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger had its length wrap, so SQLite saw only the first length mod 2^32 bytes. An attacker who controls the length of a SQL string could truncate the query, for example dropping a trailing WHERE clause.
Affected: sqlite3
⚡ ATTACK CHAIN
Attack steps:
1. Identify injectable parameters (URL params, form fields, HTTP headers, cookies).
2. Basic test: ' OR '1'='1 — look for errors or behavior changes.
3. UNION-based extraction: ' UNION SELECT user(),database()--
4. Automated: sqlmap -u 'TARGET_URL' --dbs --dump --batch
5. Time-based blind: '; IF(1=1) WAITFOR DELAY '0:0:5'--
6. Post-exploitation: dump credentials, write webshell via INTO OUTFILE '/var/www/shell.php'.
🔧 Tools: sqlmap, Burp Suite (Intruder), manual
🗺️ MITRE ATT&CK: T1190 (Exploit Public-Facing Application), T1078 (Valid Accounts)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable.
🛡️ REMEDIATION
→ Apply vendor security update for sqlite3.
→ Use prepared statements and parameterized queries.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]