Unauthenticated users can run Kubernetes tools in k8s-mcp-server versions before 1.1.0

  • k8s-mcp-server
  • authentication
  • Kubernetes
  • SSE

Missing authentication in default SSE transport enables remote access

Security flaw affects all versions prior to 1.1.0

Update to version 1.1.0 to mitigate unauthorized cluster operations

k8s-mcp-server has a vulnerability in its default SSE/HTTP transport that lets anyone with network access to the server’s listening port invoke Kubernetes tools without authentication. The flaw affects versions before 1.1.0, according to the GitHub Advisory.

Without authentication, session tokens or an Origin check, an unauthenticated client can list the available tools and call them. Operations run with the Kubernetes privileges configured for the server, so they may include reading cluster data and, when read-only mode is disabled, changing cluster state.

The issue is classified as CWE-306, Missing Authentication for Critical Function. Version 1.1.0 fixes the vulnerability.

Key terms explained

CWE-306

CWE-306 refers to a security weakness where a system fails to verify the identity of a user before allowing access to critical functions.

Think of it this way. This is like leaving the front door of a secure building unlocked, allowing anyone to walk in and access restricted areas without showing identification.