When k8s-mcp-server runs in its default SSE transport mode, the MCP tools/call
endpoint is dispatched with no authentication, session token, or Origin check.
Any client that can reach the listening port can enumerate and invoke the
server's Kubernetes tools (including destructive/write tools) without credentials,
executing with the server's configured cluster privileges.
Commit be87a6dd72bb6ec1d4886b8548843b99a4638b12 (Merge PR #130) MCP library: github.com/mark3labs/mcp-go v0.57.0 Default mode: sse (SERVER_MODE default), default port 8080, bind 0.0.0.0
server.NewSSEServer(s) is created with no auth option and no
contextFunc; L130 sse.Start(":"+port) binds all interfaces (0.0.0.0).s.server.HandleMessage(ctx, rawMessage) dispatches to the tools/call handler.Access-Control-Allow-Origin: * is present (CORS relaxation, not auth).
Write tools (Create/Delete/RolloutRestart, Helm Install/Upgrade/Uninstall/Rollback)
are all registered unless -read-only is set (default readOnly=false).Started: k8s-mcp-server -mode sse -port 8080 with a dummy non-routable
KUBERNETES_SERVER=https://127.0.0.1:1 (no real cluster touched).
GET /sse -> HTTP 200; server mints /message?sessionId=93b3... POST /message initialize -> HTTP 202; result returned over SSE POST /message tools/list -> HTTP 202; FULL tool list returned (incl. destructive) POST /message tools/call getAPIResources -> HTTP 202; handler EXECUTED: error -32603 "... Get...
1.1.0Exploitability
AV:NAC:LAT:NPR:NUI:NVulnerable System
VC:NVI:NVA:NSubsequent System
SC:HSI:HSA:H7.9/CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:HAuthentication