Skip to main content
Menu
CVEs

CVE

sqlite-mcp read-only bypass and SQL injection in describe_table

Affects sqlite-mcp versions before 0.1.2 in default read-only mode, where execute_query accepts statements after a leading SELECT, and the describe_table tool interpolates table names into a PRAGMA statement. Fixed in 0.1.2.

CVE-2026-130008EUVD-2026-129039Published Updated Summary written by a model

8.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.1.2
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

StacklokLabs sqlite-mcp has a flaw that lets a remote attacker, without logging in, get around its read-only mode by sending crafted input through the execute_query and describe_table tools. The attacker can then attach and read other SQLite database files, modify the protected database, or create SQLite-format files on the server.

Original description

sqlite-mcp is a Model Context Protocol server for SQLite. Prior to 0.1.2, the default read-only mode can be bypassed through execute_query, which accepts a leading SELECT while the SQLite driver executes trailing statements, and through describe_table, which interpolates the caller-controlled table_name into PRAGMA table_info. Either path can issue ATTACH DATABASE, which opens an attached file read-write despite mode=ro and can make the protected database writable, read other SQLite database files, or create a SQLite-format file at a path writable by the server process. Existing non-empty files that are not SQLite databases are refused and left unchanged. The server has no built-in authentication and listens on all interfaces at :8080 by default, so any client that can reach the port can invoke these tools unless an authenticating proxy is in place. This issue is fixed in version 0.1.2.

Who should check

Teams running sqlite-mcp before 0.1.2, especially any deployment reachable on port 8080 without an authenticating proxy

“In read-only mode (the default), a client that can call the MCP tools can write”

github.com

cve.now Index

33Pcve.now Index 33 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 8.2
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 0.1.2.

  • Workaround: Keep the server on a loopback or private interface, or run it behind an authenticating proxy

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130008 (sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130008 (entry last updated 2026-11-18):
Affected:
- StacklokLabs sqlite-mcp: fixed in 0.1.2
Fixed versions: 0.1.2.
Conditions (all must be true for the bug to be hit):
- Versions before 0.1.2 are affected (source: https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f)
- Default read-only mode, where the execute_query tool accepts statements after a leading SELECT (source: https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f)
- The describe_table tool, which interpolates the table name into a PRAGMA statement (source: https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Keep the server on a loopback or private interface, or run it behind an authenticating proxy (source: https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f)
CISA KEV: CVE-2026-130008 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130008 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f
- https://github.com/StacklokLabs/sqlite-mcp/pull/112
- https://github.com/StacklokLabs/sqlite-mcp/commit/1da5a6582a4f9d90c778db5687ddcd0c39d2c1ec
- https://github.com/StacklokLabs/sqlite-mcp/commit/3c244d61cc0a9c0cc5e4d74719c1dc83edcfa339
- https://github.com/StacklokLabs/sqlite-mcp/releases/tag/v0.1.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130008
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130008"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • StacklokLabs sqlite-mcp

    fixed in 0.1.2

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130008

Is CVE-2026-130008 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: cve.now feed data

What does this mean?

In read-only mode, the execute_query tool accepts extra SQL statements chained after a leading SELECT, so a client that can call the tools can modify the database that read-only mode is meant to protect. The describe_table tool also inserts its table name argument into a PRAGMA statement without a guard, which is an SQL injection. Through these, a client can also read other SQLite files the server can read and create SQLite-format files where the server can write.Source: github.com

Which versions are affected by CVE-2026-130008?

sqlite-mcp: before 0.1.2.Source: cve.now feed data

Am I affected, and how do I check?

Versions before 0.1.2 of sqlite-mcp from StacklokLabs are affected, in the default read-only mode and with the describe_table tool. To check a setup, look at the installed sqlite-mcp version and confirm whether it is below 0.1.2.Source: github.com

How do I fix CVE-2026-130008?

Upgrade to sqlite-mcp 0.1.2. If you cannot upgrade, keep the server on a loopback or private interface, or run it behind an authenticating proxy such as ToolHive.Source: github.com

More CVEs