CVE-2026-130007: k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution

Published Nov 18, 2026
·
Updated

k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVERMODE 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.

Affected Software

1 affected component
k8s-mcp-server<1.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade k8s-mcp-server to a version that resolves this vulnerability.

    Fixed in 1.1.0

Event History

Nov 18, 2026
CVE Published
via MITRE·04:38 PM
Data Sourced
via MITRE·04:38 PM
DescriptionWeakness
Data Sourced
via OSV·04:38 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unauthenticated access?

Versions prior to 1.1.0 are exposed when using the default SERVER_MODE=SSE configuration. In that mode, the service listens on 0.0.0.0:8080, so any client able to reach that port can access the SSE/HTTP transport without credentials.

2

What level of access can an attacker obtain?

An attacker who can reach the listener can enumerate and invoke registered Kubernetes tools. Because read-only mode is disabled by default, those tools may perform write operations using the Kubernetes privileges configured for the server.

3

Does an attacker need a valid session or browser origin to exploit this?

No. The sessionId created by GET /sse is only a correlation value, and POST /message accepts a loadable sessionId without authorization or Origin validation before dispatching tool calls.

4

What should be done if an immediate upgrade is not possible?

Restrict network access to port 8080 so untrusted clients cannot reach the service. Reducing the Kubernetes privileges configured for the server and enabling read-only operation can also limit the impact of unauthorized tool execution.

5

How can I determine whether my deployment is affected?

Check whether k8s-mcp-server is running a version earlier than 1.1.0 and using the SSE transport, particularly if it is listening on 0.0.0.0:8080. Affected instances accept unauthenticated requests to the SSE/HTTP endpoints and can dispatch tools/call operations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203