Is CVE-2026-46519 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46519 being exploited in the wild.

How severe is CVE-2026-46519?

High severity, with a CVSS score of 8.8, published 11 June 2026.

Which products and versions are affected?

mcp-server-kubernetes (npm) < 3.6.0, SEMVER:introduced=0,fixed=3.6.0.

Is there a fix for CVE-2026-46519?

Yes. mcp-server-kubernetes (npm): upgrade to 3.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46519 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-46519?

Check whether you run mcp-server-kubernetes (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46519: Flux159 mcp-server-kubernetes authorization bypass in tool execution

Q: Is there a fix for CVE-2026-46519?

Yes. mcp-server-kubernetes (npm): upgrade to 3.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46519 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-46519?

Check whether you run mcp-server-kubernetes (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46519 · Severity: high · CVSS 8.8 · Published 2026-06-11

mcp-server-kubernetes is a tool used to manage Kubernetes clusters through AI-driven interfaces. A security flaw allowed users to bypass configured safety restrictions, such as 'read-only' modes, to perform destructive actions like deleting resources or executing commands in containers. This could lead to unauthorized cluster-wide changes or data loss if an authenticated user or AI agent ignores the intended access limits.

Technologies: mcp-server-kubernetes (npm). Vendors: npm.

Quick answers

Is CVE-2026-46519 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46519 being exploited in the wild.
How severe is CVE-2026-46519?: High severity, with a CVSS score of 8.8, published 11 June 2026.
Which products and versions are affected?: mcp-server-kubernetes (npm) < 3.6.0, SEMVER:introduced=0,fixed=3.6.0.
Is there a fix for CVE-2026-46519?: Yes. mcp-server-kubernetes (npm): upgrade to 3.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46519 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46519?: Check whether you run mcp-server-kubernetes (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mcp-server-kubernetes (npm): upgrade to 3.6.0 or later
```
npm install mcp-server-kubernetes@3.6.0
```

Technical details

An authorization bypass exists in mcp-server-kubernetes due to 'cosmetic' access control enforcement. While the server filters available tools during the discovery phase (tools/list) based on environment variables like ALLOWED_TOOLS or ALLOW_ONLY_READONLY_TOOLS, it fails to validate these restrictions during the execution phase (tools/call). An attacker with network access and valid authentication (MCP_AUTH_TOKEN) can directly invoke sensitive tools such as 'kubectl_delete' or 'exec_in_pod' by name, even if they are hidden from the tool list. This vulnerability is rooted in src/index.ts where the CallToolRequestSchema handler lacks the filtering logic present in the ListToolsRequestSchema handler. The issue is resolved in version 3.6.0.

Affected products

Flux159 mcp-server-kubernetes < 3.6.0

Identifiers

CVE-2026-46519
GHSA-cr22-wjx7-2w6m

Timeline

2026-05-14: patched: Version 3.6.0 released
2026-05-17: advisory: GitHub Security Advisory published
2026-06-11: disclosed: CVE-2026-46519 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.