dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-41010

HIGH · 8.2 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
ReleaseJob#unpack builds job_dir = File.join(@release_dir, 'jobs', name) and job_tgz = File.join(@release_dir, 'jobs', "#{name}.tgz") where name returns @job_meta['name'], a value taken verbatim from the jobs: array of the attacker-supplied release.MF inside the uploaded tarball. These paths are then interpolated into a shell string: Bosh::Common::Exec.sh("tar -C #{job_dir} -xf #{job_tgz} 2>&1", :on_error => :return). Bosh::Common::Exec.sh executes via %x{#{command}} (bosh-common/lib/bosh/common/exec.rb:53), i.e. /bin/sh -c, so any shell metacharacters in name are interpreted. FileUtils.mkdir_p(job_dir) on line 49 creates the literal directory (no shell) and succeeds even when the name contains $()/;, so execution reaches the sh call. Affected versions: - BOSH Director: all versions prior to v282.1.12 (inclusive); fixed in v282.1.12 or later

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

BOSH Director's ReleaseJob#unpack method contains a command injection vulnerability where the job name from release.MF is taken verbatim and interpolated into a shell command via %x{} execution. An attacker can embed shell metacharacters like $() or ; in the job name to execute arbitrary commands with the privileges of the BOSH Director process.

MitigationUpgrade BOSH Director to v282.1.12 or later, which includes proper input sanitization or removes shell-based execution for this code path.

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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. Determine BOSH Director version
    Run 'bosh env' or check the BOSH Director deployment manifest/version file. On the BOSH Director VM, check /var/vcap/bosh/etc/director.yml or run 'bosh-cli director version'.
    Affected if The installed version is earlier than v282.1.12 (the fixed release).
  2. Verify BOSH Director API accessibility
    Confirm whether the BOSH Director API (typically port 25555) is accessible to untrusted or non-admin users. Check firewall rules and Cloud Foundry or BOSH deployment access controls.
    Affected if The Director API is accessible to users who should not be permitted to upload BOSH releases.
  3. Inspect recent release uploads
    Review BOSH Director audit logs or task logs for recent 'bosh upload-release' commands. Look for release.MF files that may contain unusual characters in job names.
    Affected if Suspicious or unrecognized release uploads exist in the environment, particularly from untrusted sources.
  4. Check for shell metacharacters in release.MF
    If you have access to uploaded release tarballs, extract and inspect the release.MF file. Look at the 'jobs' array entries for characters such as $`, $(, ;, |, &, >, <, or backticks.
    Affected if Any release.MF file in your environment contains shell metacharacters in job name definitions.

A user is affected if their BOSH Director version is earlier than v282.1.12 AND the Director API or release upload functionality is accessible to untrusted users who could upload a malicious release.MF file.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BOSH Director to v282.1.12 or later, which includes proper input sanitization or removes shell-based execution for this code path.

Recommended fix High confidence

BOSH Director v282.1.12 or later

  1. Back up the BOSH Director database and configuration before proceeding with the upgrade
  2. Download BOSH Director v282.1.12 or later from the Cloud Foundry release repository
  3. Follow the standard BOSH upgrade procedure to deploy the new Director version
  4. Verify the upgrade was successful by checking the Director responds and deployment operations work normally
Caveat Review BOSH release notes for any breaking changes between your current version and v282.1.12; standard upgrade precautions (backups, staging environment testing) apply

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,140
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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