What happened
k8s-mcp-server (manages Kubernetes clusters through MCP) prior to 1.1.0 defaults SERVER_MODE to SSE with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is only validated for validity, not identity, so any remote client can connect and issue MCP tools against the connected Kubernetes cluster.
Why it matters
An MCP server that gives an LLM agent write access to a Kubernetes cluster is a high-value agentic target. If the SSE endpoint is exposed without auth, anyone who can reach port 8080 can drive the cluster through the MCP tools (deploy, scale, read secrets), turning a convenience agent into an unauthenticated cluster-control surface.
Attack vector
An unauthenticated client connects to the SSE endpoint (0.0.0.0:8080) and issues MCP tools, since the server is created with no authentication/context function and sessionId carries no identity check.
Affected systems
k8s-mcp-server before 1.1.0 (SSE default)
Mitigation
Upgrade to k8s-mcp-server 1.1.0 or later, which adds server auth; bind the listener to loopback or a network policy in the interim.