CVE-2025-65719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpen Source Kubectl MCP Server v1.1.1 contains a vulnerability that allows arbitrary code execution through user interaction with a crafted HTML page. This suggests the server either renders user-supplied HTML without proper sanitization or has an endpoint that can be exploited via XSS to trigger server-side code execution, likely through the MCP server's interaction with kubectl.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Kubectl MCP Server is installedLook for the kubectl-mcp-server binary, package, or running service on the system. Common locations: /usr/local/bin/, ~/bin/, or check running processes with 'ps aux | grep -i mcp'. If installed via npm, check 'npm list -g @modelcontextprotocol/server-kubectl'Affected if The Kubectl MCP Server binary or package is found on the system
-
Determine the installed versionRun the server with --version flag, or check the package version: 'kubectl-mcp-server --version' or 'npm list -g @modelcontextprotocol/server-kubectl'Affected if The version is 1.1.1 or earlier (no fixed version was specified, so treat 1.1.1 and below as affected)
-
Check if HTTP/web server features are enabledExamine the server configuration file or environment variables for web server settings. Look for flags like --port, --host, or enable-web flags. Check if the server binds to a network interface (not localhost-only)Affected if The MCP server is configured to expose an HTTP/web interface to network users
-
Verify if HTML rendering endpoints are accessibleIf a web interface exists, test accessing common HTML endpoints or check the server logs for requests to HTML-serving routes. Review configuration for any HTML display or template rendering settingsAffected if The server exposes endpoints that render or display HTML content to users
A user is affected if Kubectl MCP Server version 1.1.1 is running with HTTP/web server features enabled that could accept or render user-supplied input as HTML.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to the patched version of Kubectl MCP Server once available; implement strict input validation and output encoding for any HTML rendering, and apply Content Security Policy headers to prevent execution of injected scripts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data