CVE-2025-15060
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 · uneditedclaude-hovercraft executeClaudeCode Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of claude-hovercraft. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the executeClaudeCode method. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-27785.
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 · high confidenceThis is a command injection vulnerability in claude-hovercraft's executeClaudeCode method. The flaw allows unauthenticated remote attackers to execute arbitrary code because user-supplied input is not validated before being passed to a system call, enabling execution in the context of the service account.
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.0/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 claude-hovercraft is installedLocate the claude-hovercraft package in your environment. Check using package managers (pip list, npm ls, gem list, etc.) or by searching for claude-hovercraft files in common installation directories.Affected if claude-hovercraft is present in your environment
-
Determine the installed versionRun the appropriate version command for your package manager (for example: pip show claude-hovercraft, npm list claude-hovercraft, or inspect the package metadata file). Record the version number.Affected if The installed version is any version prior to the vendor-supplied patch for CVE-2025-15060
-
Verify if executeClaudeCode method is enabledInspect the configuration files or settings files for claude-hovercraft. Look for any settings related to executeClaudeCode, command execution, or code execution features. Check if this method is explicitly enabled or accessible.Affected if The executeClaudeCode method is enabled or accessible in the configuration
-
Check network exposure of the serviceDetermine how claude-hovercraft is exposed. Review network bindings, firewall rules, or service definitions to see if the service port or endpoint is accessible to unauthenticated or untrusted network sources.Affected if The service is reachable by unauthenticated or untrusted users on the network
You are affected if claude-hovercraft with the executeClaudeCode method enabled is installed and accessible to untrusted users, regardless of the specific version.
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 dataImplement strict input validation and sanitization on all user-supplied strings before using them in system calls. If possible, disable the executeClaudeCode method until a patch is available, or refactor to avoid shell execution entirely.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15060 — 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-15060 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