StacklokLabs fixes sqlite-mcp flaws that bypassed read-only mode
- StacklokLabs
- sqlite-mcp
- SQL injection
- read-only
- vulnerability

Update resolves unauthorized write access and file creation risks
Flaws involved statement chaining and SQL injection vectors
Version 0.1.2 closes the flaws; the advisory recommends upgrading
StacklokLabs fixed vulnerabilities in sqlite-mcp that let clients bypass the package’s default read-only mode. The flaws affected versions earlier than v0.1.2, according to the GitHub advisory.
A client able to call the server’s tools could write to the database intended to be read-only, read other SQLite files accessible to the server process, or create SQLite files where that process could write. The advisory says the server has no built-in authentication and listens on port 8080 on all interfaces by default, so reachable deployments without an authenticating proxy were exposed.
Version 0.1.2 disables SQLite’s ATTACH capability, enables query-only mode on read-only connections, rejects multiple statements in execute_query, and uses a bound parameter for the table name in describe_table. The advisory recommends upgrading; deployments that cannot upgrade should restrict access and limit the files the server can access.




