Which versions of BOSH CLI are affected by CVE-2026-47826?

Cloud Foundry BOSH CLI versions prior to v7.10.4 contain a path traversal vulnerability enabling attackers to write arbitrary files and disclose sensitive information when operators download or sync…. A patch is available.

How to fix or mitigate CVE-2026-47826?

24 HOURS: Audit all deployed BOSH CLI versions; document which systems run versions prior to v7.10.4 and whether they've accessed external or untrusted release sources. 7 DAYS: Implement compensating controls (restrict blob downloads to signed/verified releases, enforce file-system integrity monitoring, limit operator privileges to minimum required). 30 DAYS: Apply vendor patch to v7.10.4 or later when available; if unavailable, establish air-gapped or internally-mirrored release package repositories.

BOSH CLI CVE-2026-47826

Q: What is the CVSS score of CVE-2026-47826?

CVE-2026-47826 has a CVSS 4.0 base score of 8.5 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-42507 HIGH

Path Traversal (CWE-22)

2026-07-09 vmware

GHSA-j722-97vw-3p9m

Path Traversal Bosh Cli Tool Cloudfoundry Foundation

8.5

CVSS 4.0 · Vendor: vmware

Severity by source

Vendor (vmware) PRIMARY

8.5 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.1 HIGH

Malicious blobs.yml is network-delivered but the operator must run the CLI to sync it (UI:R), no auth needed (PR:N); traversal enables file write (I:H) and file exfiltration (C:H) with no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vmware).

CVSS VectorVendor: vmware

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Patch available

Jul 09, 2026 - 08:01 EUVD

Analysis Generated

Jul 09, 2026 - 07:15 vuln.today

DescriptionCVE.org

The blobs.yml path key traversal vulnerability in the BOSH CLI tool allows an attacker to write arbitrary files and exfiltrate sensitive information. Affected versions: BOSH CLI tool versions prior to v7.10.4.

AnalysisAI

Arbitrary file write and information disclosure in the Cloud Foundry BOSH CLI tool (versions prior to v7.10.4) stems from insufficient sanitization of the path key inside blobs.yml, letting a crafted release blob spec escape the intended blobstore directory. When an operator syncs or downloads blobs from a malicious or tampered release, the CLI can write files to attacker-controlled locations on the host and expose sensitive files. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the vendor-assigned CVSS 4.0 base score is 8.5 (High).

Technical ContextAI

BOSH is Cloud Foundry's release-engineering and deployment orchestration system; the CLI packages, uploads, and syncs 'releases' whose large binary artifacts are tracked as blobs described in a config/blobs.yml manifest keyed by relative path. The vulnerability is a classic path/directory traversal (CWE-22-class) in how the CLI resolves the path key from blobs.yml: values containing traversal sequences (e.g. ../ or absolute paths) are not constrained to the blobstore working directory, so the resolved destination can point anywhere the CLI process can write. The affected component is identified by CPE cpe:2.3:a:cloudfoundry_foundation:bosh_cli_tool, i.e. the standalone BOSH CLI binary rather than a BOSH director. The same untrusted-path handling that enables writes outside the sandbox is also what permits reading/exfiltrating sensitive files, consistent with the vendor's Information Disclosure tag.

RemediationAI

Vendor-released patch: v7.10.4 - upgrade the BOSH CLI to v7.10.4 or later on all operator workstations and CI/CD runners, per the Cloud Foundry advisory (https://www.cloudfoundry.org/blog/cve-2026-47826-blobs-yaml-path-traversal-allows-file-writes/). Until upgrade is complete, the practical compensating control is to only run blob sync/download operations against releases from trusted, integrity-verified sources and to avoid processing blobs.yml from untrusted or externally-authored releases; the trade-off is reduced flexibility in consuming third-party releases. Additionally, run the CLI under a low-privilege, dedicated account with a constrained working directory so a traversal write cannot reach sensitive system paths (trade-off: may require adjusting CI permissions), and inspect blobs.yml path values for ../ or absolute paths before syncing when handling any external release.