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.
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).
How to check
- 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).
- Check whether port 8080 on those hosts or pods is reachable from other machines: ss -ltnp | grep 8080
How to fix
- Upgrade k8s-mcp-server to 1.1.0 or later and sqlite-mcp to 0.1.2 or later.
- Bind MCP servers to 127.0.0.1 or use stdio, and put network-exposed ones behind an authenticating proxy.
- 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 Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)