github.com/reza-gholizade/k8s-mcp-server · k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution
Affects github.com/reza-gholizade/k8s-mcp-serverSource GCVE Database
Not known to be exploited · CVSS 7.9 High : upgrade to 1.1.0 soon.
Data as of 19 Nov 2026, 23:22 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 7.9 |
|---|
- Patch
- Available – fixed in 1.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade github.com/reza-gholizade/k8s-mcp-server to 1.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/reza-gholizade/k8s-mcp-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in version 1.1.0 that addresses this issue. Users should upgrade to k8s-mcp-server version 1.1.0 or later. The suggested fixes include adding authorization checks on the HTTP transports, defaulting the server to bind only to localhost (127.0.0.1), and documenting that the HTTP mode must be protected by an authenticating proxy. Until patched, deployments should restrict network access to the SSE port or run the server in a mode that does not expose this unauthenticated interface.
Description
k8s-mcp-server versions prior to 1.1.0 running in default SSE transport mode expose an unauthenticated HTTP endpoint on port 8080 bound to all interfaces. This endpoint allows any network-accessible client to enumerate and invoke Kubernetes tools, including destructive operations, without authentication. The server does not enforce authorization or origin checks, and the default configuration permits state-changing commands. This vulnerability is due to missing authentication on critical functions and is classified as CWE-306.
References
- github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-130007 (opens in a new tab)
- github.com/reza-gholizade/k8s-mcp-server/issues/131 (opens in a new tab)
- github.com/reza-gholizade/k8s-mcp-server/pull/134 (opens in a new tab)
- github.com/reza-gholizade/k8s-mcp-server/commit/817d81005369837e0c034962785851ca4dec9a76 (opens in a new tab)
- github.com/reza-gholizade/k8s-mcp-server (opens in a new tab)
- github.com/reza-gholizade/k8s-mcp-server/releases/tag/v1.1.0 (opens in a new tab)