Skip to main content
Menu
CVEs

CVE

k8s-mcp-server unauthenticated tool execution in SSE/HTTP transport

Affects k8s-mcp-server 1.0.25 and earlier in the default SSE transport mode, which listens on 0.0.0.0:8080 without authentication. Fixed in 1.1.0.

CVE-2026-130007Published Updated Summary written by a model

7.9HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.1.0
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

The k8s-mcp-server software, from reza-gholizade, lets any client that can reach its network port run Kubernetes tools without logging in. Because the default setup listens on all interfaces and read-only mode is off by default, an attacker can reach it remotely and use write-capable tools with the server's cluster privileges.

Original 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.

Who should check

Teams running reza-gholizade k8s-mcp-server 1.0.25 or earlier in default SSE mode on port 8080, especially any container or host reachable over the network.

“Affected versions <= 1.0.25”

github.com

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.9/10CVSS 7.9
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 1.1.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130007 (k8s-mcp-server: Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130007 (entry last updated 2026-11-18):
Affected:
- reza-gholizade k8s-mcp-server: fixed in 1.1.0
Fixed versions: 1.1.0.
Conditions (all must be true for the bug to be hit):
- Server runs in default SSE transport mode (SERVER_MODE default), listening on 0.0.0.0:8080 (source: https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq)
- Affected versions are 1.0.25 and earlier; fixed in 1.1.0 (source: https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq)
- Write-capable tools are registered because read-only mode is off by default (source: https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130007 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130007 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq
- https://github.com/reza-gholizade/k8s-mcp-server/issues/131
- https://github.com/reza-gholizade/k8s-mcp-server/pull/134
- https://github.com/reza-gholizade/k8s-mcp-server/commit/817d81005369837e0c034962785851ca4dec9a76
- https://github.com/reza-gholizade/k8s-mcp-server/releases/tag/v1.1.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130007
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130007"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • reza-gholizade k8s-mcp-server

    fixed in 1.1.0

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130007

Is CVE-2026-130007 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The server's default SSE/HTTP transport has no authentication, so any client that can reach the listening port can list and run its Kubernetes tools with the server's cluster privileges. This includes write tools such as create, delete, rollout restart and Helm install, upgrade, uninstall and rollback.Source: github.com

Which versions are affected by CVE-2026-130007?

k8s-mcp-server: before 1.1.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.0.25 and earlier are affected when the server runs in the default SSE transport mode (SERVER_MODE default) and listens on 0.0.0.0:8080. To check, look at the installed version and the SERVER_MODE and port settings. Write tools are registered unless the -read-only flag is set, which is off by default.Source: github.com

How do I fix CVE-2026-130007?

Upgrade to k8s-mcp-server 1.1.0, which is the fixed version.Source: github.com

More CVEs