Auth bypass in Reza-Gholizade K8s-Mcp-Server
CVE-2026-130007
- CVSS
- Not scored
- Public exploits
- None known
- EPSS
- 0.004 · 31.7th percentile
- Published
- 2026-11-18
What to do
- Fixed in
1.1.0- Affected
- 1 affected product
k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults 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 a correlation value, and the POST /message handler accepts a loadable sessionId without an authorization or Origin check before dispatching tools/call; consequently, any client able to reach the port can enumerate and invoke registered Kubernetes tools without credentials. Read-only mode is disabled by default, leaving write-capable Kubernetes tools available to run with the server's configured cluster privileges. This issue is fixed in version 1.1.0.
Vulnerability class: Broken Authentication
Published · last modified .
EPSS exploit prediction
EPSS 0.004, 31.7th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Reza-Gholizade K8s-Mcp-Server — versions < 1.1.0
Weakness classification (CWE)
References
- github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq
- github.com/reza-gholizade/k8s-mcp-server/issues/131
- github.com/reza-gholizade/k8s-mcp-server/pull/134
- github.com/reza-gholizade/k8s-mcp-server/commit/817d81005369837e0c034962785851c…
- github.com/reza-gholizade/k8s-mcp-server/releases/tag/v1.1.0