WhatBrokeToday
GTA 6FAQ
Kubernetes

k8s-mcp-server Unauthenticated RCE/Tool Dispatch Vulnerability

high

Is it fixed? Not yet.

Ongoing since Nov 18, 16:38 UTC. First reported Nov 18, 16:38 UTC.

What happened

k8s-mcp-server prior to version 1.1.0 defaults to an unauthenticated SSE listener on 0.0.0.0:8080 that lacks session authorization or Origin checks on the POST /message handler. This allows arbitrary clients to dispatch tools/call and interact with managed Kubernetes clusters.

What caused it?

The SSE server in main.go is created without an authentication option or context function, and the POST /message handler accepts loadable sessionId values without checking authorization or Origin headers prior to dispatching tools/call.

Source: tenable.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    k8s-mcp-server manages Kubernetes clusters: CVE-2026-130007 (High)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    k8s-mcp-server manages Kubernetes clusters: CVE-2026-130007 (High)(opens security advisory in a new tab)

    High severity. 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…

    by Tenable 0upvotes 0comments

FAQ

What happened in the Kubernetes issue?

k8s-mcp-server prior to version 1.1.0 defaults to an unauthenticated SSE listener on 0.0.0.0:8080 that lacks session authorization or Origin checks on the POST /message handler. This allows arbitrary clients to dispatch tools/call and interact with managed Kubernetes clusters.

What is affected by the Kubernetes issue?

Kubernetes (versions: < 1.1.0).

When did the Kubernetes issue start and end?

It started Nov 18, 16:38 UTC and is still ongoing (12 h 5 min so far). This page updates as it develops.

How do I get alerts for Kubernetes?

Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.