CVE-2026-130008

sqlite-mcp read-only mode could still modify SQLite files

StacklokLabs · sqlite-mcp

First documented disclosure · Review checkpoint

Summary

A tool caller could bypass read-only access and reach other SQLite files.

Severity and exploitation evidence

High · 8.2/10 · CVSS 3.1. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Statement chaining and an interpolated table name permitted ATTACH, which opened attached databases read-write.

Conditions required

Access to MCP tools; the default listener has no built-in authentication and binds all interfaces.

Potential impact

Protected SQLite data can be changed, other SQLite databases read, and new SQLite-format files created. Existing nonempty non-SQLite files are not overwritten.

Affected versions and configurations

sqlite-mcp: < 0.1.2.

Fix and mitigation status

0.1.2.

Practical next steps

Apply the issue-specific correction: 0.1.2. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Enforce database restrictions in the engine and on every pooled connection.

Evidence and limits

Earliest reviewed public evidence 2026-10-19; CVE publication 2026-11-18. CVSS 3.1 8.2 is attributed to GitHub_M in the CNA record.

Sources