UTC
High

sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table

CVE-2026-130008 · GHSA-q433-mp6c-8v4f · published 2026-11-19

Severity
High
CVSS score
8.2
Chance of exploitation (EPSS)
0.36%
Fixed in
0.1.2
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

Modify the database that read-only mode is meant to protect. Read any SQLite database file the server process can read. Create new SQLite-format files anywhere the server process can write, or write to existing SQLite or empty files. Existing non-empty files that are not SQLite databases are refused and left unchanged. The server has no built-in authentication and, by default, listens on :8080 on all interfaces. Unless it is deployed behind an authenticating proxy, anyone who can reach that port can exploit this.

What to do

Upgrade github.com/StacklokLabs/sqlite-mcp to 0.1.2 or later.

Fixed in v0.1.2: ATTACH is disabled in the engine (SQLITE_LIMIT_ATTACHED set to 0) on every connection that runs a statement. Read-only connections set query_only. execute_query rejects input that contains more than one statement. describe_table passes the table name as a bound parameter.

If you cannot upgrade yet

Upgrade to v0.1.2. If you cannot upgrade, don't expose the server to untrusted clients: keep it on a loopback or private interface, or run it behind an authenticating proxy such as ToolHive. Mount only the database you intend to expose, read-only at the filesystem or container level.

Affected
PackageRegistryAffectedFixed in
github.com/StacklokLabs/sqlite-mcpGo< 0.1.20.1.2

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].