Skip to main content
VulnerabilityPublished

CVE-2026-130008: StacklokLabs sqlite-mcp · SQL Injection

Affects StacklokLabs sqlite-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.1.2 soon.

Data as of 18 Nov 2026, 17:05 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.2
Patch
Available – fixed in 0.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade StacklokLabs sqlite-mcp to 0.1.2.

Affected software

ProductAffectedFixed in
StacklokLabssqlite-mcpAffected
  • <0.1.2
Fixed in
  • 0.1.2

AI-suggested

Upgrade sqlite-mcp to version 0.1.2 or later, where this vulnerability is fixed. Until upgraded, restrict network access to the server port (8080) using firewalls or an authenticating proxy to prevent unauthorized clients from reaching the service.

Description

sqlite-mcp versions prior to 0.1.2 contain an SQL injection vulnerability that allows bypassing the default read-only mode. This occurs via the execute_query and describe_table functions, enabling attackers to execute ATTACH DATABASE commands. The vulnerability can lead to unauthorized write access to the protected database, reading other SQLite database files, or creating SQLite-format files in writable locations. The server lacks built-in authentication and listens on all interfaces by default, exposing it to any client able to reach port 8080. The issue is fixed in version 0.1.2.

References

Community reviews

Loading reviews…