Skip to content
HighVulnerability

GHSA-m932-63jc-4jqq: k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution

Published
Record updated
View JSON
Affected
  • github.com/reza-gholizade/k8s-mcp-server < 1.1.0
Fixed in
1.1.0
  • released August 31, 2026, 80 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.4%

Summary

k8s-mcp-server at commit be87a6dd72bb6ec1d4886b8548843b99a4638b12 (Merge PR #130), using mcp-go v0.57.0, exposes its MCP tools/call endpoint on the default SSE transport (port 8080, bound to 0.0.0.0) with no authentication, session token or Origin check. Any client that can reach the port can list and invoke Kubernetes tools, including write tools such as Create, Delete and Helm Install/Upgrade/Uninstall/Rollback, using the server's configured cluster privileges unless -read-only is set. This is classified as CWE-306 (Missing Authentication for Critical Function).

Mitigation

Suggested fix from the source: add an authorization gate before tools/call on the HTTP transports, for example WithSSEContextFunc to validate an Authorization bearer token, or fail closed when no token is configured in HTTP mode. Default the bind to 127.0.0.1 and require explicit opt-in for external binding. Document that HTTP mode must sit behind an authenticating proxy, and recommend STDIO by default.