CVE-2026-130008
sqlite-mcp read-only bypass and SQL injection in describe_table
Remote attackers without login can read other database files, modify the protected one, or create files on the server.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v0.1.2 | github.com/StacklokLabs/sqlite-mcp · -30 d desde divulgación | |
| Divulgación | Publicada | CVE-2026-130008 divulgada · CVSS 8.2 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
StacklokLabs sqlite-mcp has a flaw that lets a remote attacker, without logging in, get around its read-only mode by sending crafted input through the execute_query and describe_table tools. The attacker can then attach and read other SQLite database files, modify the protected database, or create SQLite-format files on the server.
Affects sqlite-mcp versions before 0.1.2 in default read-only mode, where execute_query accepts statements after a leading SELECT, and the describe_table tool interpolates table names into a PRAGMA statement. Fixed in 0.1.2.
Descripción original del registro (GitHub_M)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/StacklokLabs/sqlite-mcp |
Corregida | v0.1.2 | -30 d | v0.1.2 no afectada |
0.1.2v0.1.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/StacklokLabs/sqlite-mcp/security/advisories/GHSA-q433-mp6c-8v4fhttps://github.com/StacklokLabs/sqlite-mcp/pull/112https://github.com/StacklokLabs/sqlite-mcp/commit/1da5a6582a4f9d90c778db5687ddcd0c39d2c1echttps://github.com/StacklokLabs/sqlite-mcp/commit/3c244d61cc0a9c0cc5e4d74719c1dc83edcfa339https://github.com/StacklokLabs/sqlite-mcp/releases/tag/v0.1.2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
