CVE-2025-65719 — kubectl-mcp-server
CRITICALCVE-2025-65719 is a critical-severity (CVSS 9.8) Code Injection vulnerability in kubectl-mcp-server. A fix is available for kubectl-mcp-server — see the affected versions and patch details below.
Open Source Kubectl MCP Server vulnerable to arbitrary code execution via user interaction with crafted HTML page
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-65719.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
kubectl-mcp-servernpmDescription
An issue in Open Source Kubectl MCP Server v1.1.1 allows attackers to execute arbitrary code on a victim system via user interaction with a crafted HTML page.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | kubectl-mcp-server | all versions | 1.2.0npm install kubectl-mcp-server@1.2.0 |
| 🐍PyPI | kubectl-mcp-server | all versions | 1.2.0pip install --upgrade 'kubectl-mcp-server==1.2.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kubectl-mcp-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kubectl-mcp-server to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-65719 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2025-65719 in your dependencies?
Find it across npm, PyPI, including transitive dependencies.