Unauthorized Kubernetes operations via unchecked tool calls
Published Jun 11, 2026 · Updated Jun 11, 2026
Incorrect authorization in MCP Server Kubernetes before 3.6.0 allows remote authenticated users to invoke restricted Kubernetes tools. The CallToolRequestSchema handler in src/index.ts dispatches named tools without applying the allow-set filtering used by ListToolsRequestSchema. Access to the MCP endpoint is required, and resulting cluster read, write, execution, or deletion capabilities are bounded by the server's Kubernetes credentials.
Summary
What happened
Incorrect authorization in MCP Server Kubernetes before 3.6.0 allows remote authenticated users to invoke restricted Kubernetes tools. The CallToolRequestSchema handler in src/index.ts dispatches named tools without applying the allow-set filtering used by ListToolsRequestSchema. Access to the MCP endpoint is required, and resulting cluster read, write, execution, or deletion capabilities are bounded by the server's Kubernetes credentials.
The record
- CVE
- CVE-2026-46519
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Flux159
- Product
- MCP Server Kubernetes
- Classifications
- CWE-863, T1609
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Direct tools/call restriction-bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo