CVE-2026-130008 is a high-severity (CVSS 8.2) SQL Injection vulnerability in github.com/StacklokLabs/sqlite-mcp. A fix is available for github.com/StacklokLabs/sqlite-mcp — see the affected versions and patch details below.
sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-130008.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/StacklokLabs/sqlite-mcpReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
In read-only mode (the default), a client that can call the MCP tools can write to the database the server is meant to expose read-only, read other SQLite files, and create new SQLite files anywhere the server process can write. There are two ways in: statement chaining through execute_query, and SQL injection through describe_table.
Details
- Statement chaining in
execute_query. The only check was that the query starts withSELECT. Themodernc.org/sqlitedriver runs every;-separated statement in one call, so anything afterSELECT 1;ran unchecked. - SQL injection in
describe_table. Thetable_nameargument was interpolated intoPRAGMA table_info(%s)with no guard. - Escaping read-only mode. Through either path,
ATTACH DATABASEopens a file read-write regardless of the main connection'smode=ro. Attaching the protected database itself made it writable. Attaching another path read that file, or created it if it did not exist.
Read-write mode is not affected beyond its intended capabilities, apart from ATTACH reaching files other than the configured database.
Impact
- 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.
Patches
Fixed in v0.1.2:
ATTACHis disabled in the engine (SQLITE_LIMIT_ATTACHEDset to 0) on every connection that runs a statement.- Read-only connections set
query_only. execute_queryrejects input that contains more than one statement.describe_tablepasses the table name as a bound parameter.
Workarounds
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.
Credits
Reported by @bebold6133.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/StacklokLabs/sqlite-mcp | all versions | 0.1.2go get github.com/StacklokLabs/sqlite-mcp@v0.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/StacklokLabs/sqlite-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/StacklokLabs/sqlite-mcp to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-130008 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is CVE-2026-130008 in your dependencies?
Find it across Go, including transitive dependencies.