CVE-2025-69902
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 · uneditedA command injection vulnerability in the minimal_wrapper.py component of kubectl-mcp-server v1.2.0 allows attackers to execute arbitrary commands via injecting arbitrary shell metacharacters.
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 confidenceA command injection vulnerability in minimal_wrapper.py of kubectl-mcp-server v1.2.0 allows attackers to execute arbitrary commands by injecting shell metacharacters into input processed by this component.
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 kubectl-mcp-server installationRun 'kubectl-mcp-server --version' or check the package manifest (e.g., pip show kubectl-mcp-server, npm list kubectl-mcp-server) to determine the installed versionAffected if Installed version is v1.2.0 or the version cannot be determined but the software is present
-
Locate minimal_wrapper.py in the installationFind the minimal_wrapper.py file in the kubectl-mcp-server installation directory (common paths: node_modules/@modelcontextprotocol/server-kubectl/, Python site-packages, or /usr/local/lib/)Affected if The file minimal_wrapper.py exists in the installation and is being used by the application
-
Verify command execution contextInspect any configuration or code that invokes minimal_wrapper.py and check if it processes user-supplied input that could contain shell metacharactersAffected if User-controlled data flows to functions in minimal_wrapper.py that execute system commands without sanitization
-
Assess network exposure of the serviceCheck if kubectl-mcp-server is bound to a network interface accessible from untrusted sources (review systemd service files, Docker expose directives, or process listening addresses)Affected if The service listens on a non-loopback address or is exposed via container port mappings accessible from outside localhost
You are affected if kubectl-mcp-server v1.2.0 is installed and user-supplied input can reach the minimal_wrapper.py component via network exposure or direct invocation.
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 kubectl-mcp-server to a patched version if available; otherwise, implement strict input validation/sanitization on all user-supplied data passed to shell commands and restrict network exposure of the service.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69902 — 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-69902 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