Skip to main content
CVE-2026-46519VulnerabilityPublished Updated

mcp-server-kubernetes Affected By Tool Access Control Bypass: Presentation-Layer Filtering Without Execution-Layer

Affects mcp-server-kubernetesSource GCVE Database

0
Compare
Authoritative record:CVE-2026-46519· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 3.6.0 soon.

Data as of 30 Oct 2026, 07:30 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade mcp-server-kubernetes to 3.6.0.

Affected software

ProductAffectedFixed in
Homebrewmcp-server-kubernetespkg:brew/mcp-server-kubernetesOther threatsAffected
  • >=2.9.1 <3.6.0
Fixed in
  • 3.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

mcp-server-kubernetes is a Model Context Protocol server for Kubernetes cluster management. Prior to version 3.6.0, mcp-server-kubernetes exposes three environment variables (ALLOW_ONLY_READONLY_TOOLS, ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS, ALLOWED_TOOLS) documented as access controls for restricting which Kubernetes operations are available. These controls are enforced at the tool discovery layer (tools/list) but not at the execution layer (tools/call). Any client that knows a tool name can invoke it directly regardless of the configured restriction mode. The access control was effectively cosmetic. This issue has been patched in version 3.6.0.

References

Community reviews

Loading reviews…