dbcve.org
Cloud CliApplication · Cloudcli

CVE-2026-31862

HIGH · 8.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 1.24.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Cloud CLI (aka Claude Code UI) is a desktop and mobile UI for Claude Code, Cursor CLI, Codex, and Gemini-CLI. Prior to 1.24.0, multiple Git-related API endpoints use execAsync() with string interpolation of user-controlled parameters (file, branch, message, commit), allowing authenticated attackers to execute arbitrary OS commands. This vulnerability is fixed in 1.24.0.

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 confidence

Multiple Git-related API endpoints in Cloud CLI (versions prior to 1.24.0) use execAsync() with string interpolation of user-controlled parameters (file, branch, message, commit), allowing authenticated attackers to inject and execute arbitrary OS commands through the affected Git API functions.

MitigationUpgrade to version 1.24.0 or later, which implements secure handling of user-controlled parameters in execAsync() calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud CliApplication
Affected:< 1.24.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cloud CLI version
    Run `cloudcli --version` or check the package manager output (e.g., `npm list cloudcli` if installed via npm, or check the binary version)
    Affected if The version number returned is lower than 1.24.0 (e.g., 1.23.x, 1.22.x, etc.)
  2. Verify Git API endpoint exposure
    Check API gateway or proxy configurations for routes matching patterns like `/git/*`, `/api/git/*`, or similar Git-related endpoints exposed by Cloud CLI
    Affected if Git-related API endpoints (file, branch, message, commit handlers) are publicly or loosely accessible
  3. Confirm execAsync Git module is loaded
    Inspect running Cloud CLI process or configuration files for loaded modules related to Git operations (look for imports of Git execution modules in the codebase or runtime environment)
    Affected if The Git execution module using execAsync is present and loaded in the running configuration
  4. Check authentication settings on Git endpoints
    Review access control lists, API authentication configurations, or IAM policies governing the Git API endpoints
    Affected if Git API endpoints allow access from untrusted or unauthenticated users, or use weak authentication
  5. Audit recent Git command logs
    Examine Cloud CLI logs, system audit logs, or command execution logs for patterns of Git commands with unusual parameters (especially those containing shell metacharacters like `;`, `|`, `&`, `$()`, backticks)
    Affected if Logs show Git commands with suspicious parameter patterns indicative of injection attempts

The environment is affected if Cloud CLI version is below 1.24.0 AND Git-related API endpoints are accessible, as the execAsync function with unsanitized user input enables command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.24.0 or later
Fixed in 1.24.0
Interim mitigation

Upgrade to version 1.24.0 or later, which implements secure handling of user-controlled parameters in execAsync() calls.

Recommended fix High confidence

1.24.0

  1. Check the currently installed version of Cloud CLI (e.g., cloud --version or cloud cli --version)
  2. Upgrade Cloud CLI to version 1.24.0 or later using the appropriate package manager or installation method (e.g., npm install -g cloud@latest, pip install --upgrade cloud, or download from the official source)
  3. Verify the upgrade was successful by checking the installed version matches or exceeds 1.24.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Cli Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31862 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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