sqlite-mcp advisory: read-only mode bypassed via query chaining and SQL injection
GitHub's advisory for sqlite-mcp describes two paths that let an MCP client write to a database meant to be read-only, and it rates the flaw high severity. The fix is in v0.1.2. TechDots has not independently verified the findings.
The GitHub Advisory Database has published GHSA-q433-mp6c-8v4f, tracked as CVE-2026-130008, against sqlite-mcp, an MCP server that exposes SQLite databases to clients. According to the advisory, the server's default read-only mode can be bypassed. [1]
The advisory names two routes in. The first is statement chaining through execute_query, where only a leading SELECT was checked and any statements separated by semicolons ran unchecked. The second is SQL injection through describe_table, where the table_name argument was placed directly into a PRAGMA statement. [1]
Per the advisory, ATTACH DATABASE opens files read-write even when the main connection is read-only. That would let a client modify the protected database, read other SQLite files the process can access, and create new SQLite-format files where the process has write permission. [1]
The advisory also notes that the server has no built-in authentication and by default listens on port 8080 on all interfaces. Unless it sits behind an authenticating proxy, anyone who can reach that port could exploit the flaw. [1]
The maintainers' fix in v0.1.2 disables ATTACH at the engine level, sets query_only on read-only connections, rejects multi-statement input in execute_query, and binds the table name as a parameter in describe_table. GitHub rates the issue high severity with a CVSS score of 8.2. The advisory credits a reporter identified as @bebold6133. [1]
What we couldn't confirm
- No independent confirmation of the flaws beyond the GitHub advisory; the maintainers' own statement was not found in the source material.
- No information on whether the issue has been exploited in the wild; the advisory does not state exploitation status.
- No count of exposed or internet-facing sqlite-mcp deployments.
- The CVE record for CVE-2026-130008 was not separately checked against NVD or the CVE program.
- Advisory does not say whether the reporter's disclosure was coordinated with the maintainers or when v0.1.2 was released.
Sources
- GitHub Advisory Database: GHSA-q433-mp6c-8v4f (CVE-2026-130008): sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_tableSource published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
nginx2root: five new nginx bugs, patch now and lock origins to Cloudflare
F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026. Five memory corruption flaws, named nginx2root by Xint, can crash workers or run commands, and one HTTP/2 bug is the most widespread. Cloudflare says its edge is unaffected and that its proxy shields origins from the HTTP/2 and HTTP/3 attacks, but patching is still required.
Etherpad pre-auth file read flaw rated critical in GitHub advisory
GitHub Advisory Database has published an advisory for an unauthenticated file-read flaw in Etherpad's /static/* handler, affecting ep_etherpad-lite versions 1.8.14 up to 3.3.3 and fixed in 3.3.3. The advisory rates it critical, CVSS 9.8.