CVE-2026-119586

SQLite CLI through 3.54.1 Command Injection via .recover Output

Published Oct 30, 2026 CVSS 4.0 · 8.5 High EPSS 1.5% KEV · Not listed
Description
SQLite command-line shell through 3.54.1 contains a command injection vulnerability in the .recover command that emits attacker-planted dot-commands stored in sqlite_schema.sql values verbatim. Attackers can craft a database whose schema holds a valid CREATE statement followed by a .shell or .system line, executing OS commands when victims pipe .recover output into sqlite3.

Analysis

AI-generated

Technical impact

SQLite’s command‑line shell up to version 3.54.1 allows a .recover command to emit dot‑commands stored in the sqlite_schema.sql values verbatim. An attacker who can inject a CREATE statement followed by a .shell or .system line into a database schema can cause the shell to execute arbitrary OS commands when a victim pipes the .recover output into sqlite3. This results in arbitrary code execution, compromising confidentiality, integrity, and availability of the host system.

Affected Systems

The vulnerability affects the SQLite:SQLite product, specifically releases up to 3.54.1 of the command‑line shell. No sub‑products or separate components are identified; the flaw resides in the core SQLite engine and its shell interface.

Risk and Exploitability

The CVSS score is 8.5, indicating high severity. The EPSS score is not available, but the lack of an official KEV listing does not diminish the potential impact. Likely attack vector is local: an adversary must be able to craft and supply a malicious database and invoke a sqlite3 session that pipes .recover output. The impact is the arbitrary execution of system commands. Based on the description, exploitation requires an environment where the victim runs the sqlite3 command against a controlled database, so the risk is higher for systems that automatically process untrusted SQLite databases.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade SQLite to the latest release (≥ 3.54.2) that fixes the .recover command‑injection flaw.
  • If an upgrade cannot be performed immediately, inspect and remove any .shell or .system lines from the sqlite_schema.sql values before piping .recover output into sqlite3.
  • Restrict write permissions on SQLite database files to trusted users only and monitor for unauthorized schema modifications.
  • Disable or tightly control the use of the .recover command in environments that may handle untrusted databases.

Generated by OpenCVE AI on October 31, 2026 at 01:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description SQLite command-line shell through 3.54.1 contains a command injection vulnerability in the .recover command that emits attacker-planted dot-commands stored in sqlite_schema.sql values verbatim. Attackers can craft a database whose schema holds a valid CREATE statement followed by a .shell or .system line, executing OS commands when victims pipe .recover output into sqlite3.
Title SQLite CLI through 3.54.1 Command Injection via .recover Output
First Time appeared Sqlite
Sqlite sqlite
Weaknesses CWE-77
CPEs cpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*
Vendors & Products Sqlite
Sqlite sqlite
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 8.5, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-77

    Improper Neutralization of Special Elements used in a Command ('Command Injection')

  • CWE-78

    Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 30, 2026, 4:19 PM
Reserved
Oct 30, 2026, 11:14 AM
Status
Analyzed
Published
Oct 30, 2026, 12:16 PM
Modified
Nov 3, 2026, 3:29 PM
Severity
Important
Public date
Oct 30, 2026, 11:31 AM