dbcve.org
Bosh CliApplication · Cloudfoundry

CVE-2026-41857

HIGH · 7.8 CVSS v3.0 Published 2026-07-09
Fix available
A fix is available. Upgrade to 7.10.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges 6 weeks old

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
A compromised or malicious BOSH Director can execute arbitrary shell commands on the operator's workstation when the operator runs bosh ssh (or bosh scp/bosh logs -f) with default flags. Affected versions: BOSH CLI versions prior to 7.10.5.

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

A compromised BOSH Director can inject and execute arbitrary shell commands on the operator's workstation through the bosh ssh, bosh scp, and bosh logs -f commands when using default flags. This enables a server-side compromise to pivot to client-side remote code execution on the operator's machine.

MitigationUpgrade BOSH CLI to version 7.10.5 or later to remediate this vulnerability.

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
Bosh CliApplication
Affected:< 7.10.5

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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. Verify bosh CLI is installed
    Run `bosh --version` or `bosh -v` to confirm the CLI is present on the system
    Affected if If the command returns a version number, the bosh CLI is installed and may be affected
  2. Determine installed bosh CLI version
    Run `bosh --version` and note the version number in the output (format typically shows as 'version X.Y.Z')
    Affected if The specific version displayed is the one to evaluate against the affected range
  3. Compare version against affected range
    Compare the installed version to the affected range: versions < 7.10.5 are vulnerable. For example, if you have 7.10.4, 7.9.0, or any version lower than 7.10.5, you are in the affected range
    Affected if If the installed version is lower than 7.10.5 (e.g., 7.10.4, 7.10.0, 7.9.1, 7.0.0), the CLI is vulnerable to the injection flaw
  4. Identify usage of affected commands with default flags
    Review any automation, scripts, or workflows that invoke `bosh ssh`, `bosh scp`, or `bosh logs -f` commands. Check if these commands are run with default flags (no explicit security flags that would disable command injection)
    Affected if If these commands are used with default flags against a potentially compromised BOSH Director, arbitrary shell commands could be executed on the operator's workstation

You are affected if the installed bosh CLI version is lower than 7.10.5 and you use bosh ssh, bosh scp, or bosh logs -f commands with default flags against your BOSH Director.

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 7.10.5 or later
Fixed in 7.10.5
Interim mitigation

Upgrade BOSH CLI to version 7.10.5 or later to remediate this vulnerability.

Recommended fix High confidence

BOSH CLI 7.10.5

  1. Check current BOSH CLI version by running: bosh --version
  2. Upgrade BOSH CLI to version 7.10.5 or later. If installed via Ruby gem, run: gem install bosh_cli -v 7.10.5
  3. If installed via binary download, download the latest release from the BOSH releases page (e.g., GitHub cloudfoundry/bosh-cli)
  4. Verify the upgrade was successful by running: bosh --version
  5. Ensure the version shows 7.10.5 or higher

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

Fix this in Bosh Cli Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41857 — 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-41857 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