CVE-2026-130008: sqlite-mcp · Read-only mode bypass via statement chaining and SQL injection in describe_table
Affects github.com/StacklokLabs/sqlite-mcpSource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 0.1.2 soon.
Data as of 19 Nov 2026, 23:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
- Patch
- Available – fixed in 0.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade github.com/StacklokLabs/sqlite-mcp to 0.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/StacklokLabs/sqlite-mcp | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to sqlite-mcp version 0.1.2 or later, which disables ATTACH commands, enforces query-only mode on read-only connections, rejects multi-statement queries in execute_query, and uses parameterized queries in describe_table. If upgrading is not possible, restrict server exposure by binding it to loopback or private interfaces, or place it behind an authenticating proxy such as ToolHive. Additionally, mount only the intended database in read-only mode at the filesystem or container level to limit attack surface.
Description
sqlite-mcp versions prior to 0.1.2 allow bypassing read-only mode protections via statement chaining in execute_query and SQL injection in describe_table. This enables unauthorized write access to databases intended to be read-only, reading arbitrary SQLite files, and creating new SQLite files where the server process can write. The server lacks built-in authentication and listens on all interfaces by default, increasing exposure risk. The issue is fixed in version 0.1.2 by disabling ATTACH, enforcing query-only mode, rejecting multi-statement queries, and parameterizing inputs.
References
- github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4f (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-130008 (opens in a new tab)
- github.com/StacklokLabs/sqlite-mcp/pull/112 (opens in a new tab)
- github.com/StacklokLabs/sqlite-mcp/commit/1da5a6582a4f9d90c778db5687ddcd0c39d2c1ec (opens in a new tab)
- github.com/StacklokLabs/sqlite-mcp/commit/3c244d61cc0a9c0cc5e4d74719c1dc83edcfa339 (opens in a new tab)
- github.com/StacklokLabs/sqlite-mcp (opens in a new tab)
- github.com/StacklokLabs/sqlite-mcp/releases/tag/v0.1.2 (opens in a new tab)