CVE-2026-130007

7.9High

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.9CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
Limited impact
Weakness
CWE-306

What an attacker gets

Unauthenticated attackers can remotely execute Kubernetes tools with the server's cluster privileges. They only need network access to the server's port 8080.

Root cause

The SSE and message handlers lack authentication checks and origin validation for session IDs.

Affected versions

k8s-mcp-server prior to 1.1.0

CVSS v4.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:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to version 1.1.0 or later. Immediately restrict network access to port 8080 via firewall rules to allow only trusted sources.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-130007