← All advisories
CVE-2026-130007highBroken access control2026-11-18

k8s-mcp-server and Stacklok's sqlite-mcp listened on 0.0.0.0:8080 with no auth: anyone on the network could run Kubernetes tools or bypass SQLite read-only mode (CVE-2026-130007, CVE-2026-130008)

Two MCP servers with the same risky defaults got CVEs on 18 November 2026. reza-gholizade/k8s-mcp-server before 1.1.0 defaults to SSE on 0.0.0.0:8080 without any authentication, and read-only mode is off by default, so anyone who can reach the port can list and call write-capable Kubernetes tools with the server's cluster privileges. StacklokLabs/sqlite-mcp before 0.1.2 also listens unauthenticated on :8080, and its read-only mode can be bypassed with stacked statements or SQL injection to ATTACH other database files read-write.

01.

What it is

CVE-2026-130007 / GHSA-m932-63jc-4jqq (k8s-mcp-server <= 1.0.25, CWE-306): main.go creates the SSE server without an authentication option or context function. GET /sse issues a sessionId that is only a correlation value, and POST /message dispatches tools/call for any loadable sessionId with no authorization or Origin check. Fixed in 1.1.0 (31 August 2026).

CVE-2026-130008 / GHSA-q433-mp6c-8v4f (sqlite-mcp < 0.1.2): execute_query accepts a leading SELECT while the SQLite driver runs trailing statements, and describe_table interpolates table_name into PRAGMA table_info. Either path can issue ATTACH DATABASE, which opens a file read-write despite mode=ro. That can make the protected database writable, read other SQLite files, or create a SQLite-format file anywhere the process can write; existing non-SQLite files are refused. Fixed in 0.1.2 (19 October 2026).

02.

How to check

  1. Find these servers in your MCP configs, Helm charts or Docker setups and check their versions (k8s-mcp-server below 1.1.0, sqlite-mcp below 0.1.2).
  2. Check whether port 8080 on those hosts or pods is reachable from other machines: ss -ltnp | grep 8080
03.

How to fix

  1. Upgrade k8s-mcp-server to 1.1.0 or later and sqlite-mcp to 0.1.2 or later.
  2. Bind MCP servers to 127.0.0.1 or use stdio, and put network-exposed ones behind an authenticating proxy.
  3. Give k8s-mcp-server a least-privilege service account, and enable read-only mode where you don't need writes.
ss -ltnp | grep ':8080'
# from another host: does the SSE endpoint answer without credentials?
curl -sN --max-time 3 http://HOST:8080/sse | head -3
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.