cve.bz

CVE-2026-130008 sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table

8.2 highEPSS 0.4%Fix available

High (8.2) in stackloklabs sqlite-mcp. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/StacklokLabs/sqlite-mcp 0.1.2.

On this page
sqlite-mcp is a Model Context Protocol server for SQLite. Prior to 0.1.2, the default read-only mode can be bypassed through execute_query, which accepts a leading SELECT while the SQLite driver executes trailing statements, and through describe_table, which interpolates the caller-controlled table_name into PRAGMA table_info. Either path can issue ATTACH DATABASE, which opens an attached file read-write despite mode=ro and can make the protected database writable, read other SQLite database files, or create a SQLite-format file at a path writable by the server process. Existing non-empty files that are not SQLite databases are refused and left unchanged. The server has no built-in authentication and listens on all interfaces at :8080 by default, so any client that can reach the port can invoke these tools unless an authenticating proxy is in place. This issue is fixed in version 0.1.2.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/StacklokLabs/sqlite-mcp (Go): fixed in 0.1.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-130008 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-130008?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-130008?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-130008 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
StacklokLabs sqlite-mcp< 0.1.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q433-mp6c-8v4fGogithub.com/StacklokLabs/sqlite-mcp<0.1.20.1.2

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON