SQLite Command-Line Shell (<= 3.54.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/sqlite-command-line-shell--3.54.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 30 Oct 2026 13:30:02 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSQLite: Command injection in .recover command (CVE-2026-119586)https://feed.craftedsignal.io/briefs/2026-10-sqlite-recover-injection/Fri, 30 Oct 2026 13:30:02 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-sqlite-recover-injection/The SQLite command-line shell through version 3.54.1 is vulnerable to command injection because the .recover command emits malicious dot-commands stored in the database schema, which execute when the output is piped back into the shell.SQLite command-line shell versions up to and including 3.54.1 contain a command injection vulnerability in the .recover functionality. When a database contains a specially crafted 'sqlite_schema' table entry, the .recover command includes attacker-controlled dot-commands (e.g., .shell or .system) in its output. If a victim executes the .recover command and redirects or pipes the resulting output into an active SQLite shell session, the injected system commands will execute with the privileges of the user running the shell.

Attack Chain

  1. Attacker creates a malicious database file containing a crafted sqlite_schema entry.
  2. Attacker injects a malicious dot-command (e.g., .shell id) into the schema metadata.
  3. Attacker lures or forces a victim to run the SQLite shell and execute the .recover command on the malicious database.
  4. The .recover command outputs the attacker's malicious dot-commands to standard output.
  5. The victim pipes this output into a new or existing sqlite3 process.
  6. The sqlite3 shell interprets the piped input, parses the dot-commands, and executes the malicious OS command.

Recommendation

  1. Identify and inventory all systems utilizing the SQLite command-line shell (sqlite3) through version 3.54.1.
  2. Update all instances of the SQLite command-line shell to a version beyond 3.54.1 as soon as a patch becomes available.
  3. Implement strict controls over the execution of the .recover command on untrusted or externally sourced database files.
  4. Use the hunt lead below to identify potential usage of the .recover command in automated pipelines where redirection may occur.
]]>highadvisorysqlitecommand-injectionvulnerability