Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network access to BOSH management plane
-
DeliveryIdentify Windows host running BOSH CLI
-
ExploitCraft input with PowerShell metacharacter injection payload
-
ExecutionSubmit payload to BOSH CLI command processing
-
PersistInjected shell commands execute under CLI process context
-
ImpactAchieve full system compromise (C:H/I:H/A:H)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be on the same adjacent network segment as the Windows host running BOSH CLI - internet-based exploitation is ruled out by AV:A. The vulnerability is Windows-platform-specific; Linux deployments of BOSH CLI are not indicated as affected. High attack complexity (AC:H) implies additional specific conditions must be met, but the exact triggering configuration or CLI subcommand is not described in available data - this is a gap that defenders should resolve by reviewing the vendor advisory. The PR:N metric confirms no authentication is required once adjacency is established, removing credential-based barriers. Limiting factors include: adjacent network access only (significant geographic/topological constraint), Windows-only platform scope, and unspecified high-complexity preconditions that may further narrow exploitability. Defenders in environments that do not run BOSH CLI on Windows are not exposed to this specific attack path. |
| Impact | The CVSS vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yields a score of 7.5, reflecting full CIA impact but tempered by adjacent-only reach and high attack complexity. Adjacent network access (AV:A) limits the exploitable population to attackers already inside Cloud Foundry management network segments - this is a meaningful constraint that reduces internet-scale risk significantly. High attack complexity (AC:H) implies specific conditions must align, though these conditions are not detailed in available data; this creates uncertainty about how reproducibly the vulnerability can be triggered. No EPSS score was provided in the input data, so exploitation probability cannot be quantified. No CISA KEV listing exists, and no public exploit code has been identified - exploitation status is 'no public exploit identified at time of analysis.' The combination of AV:A and AC:H substantially limits blast radius compared to a network-facing, low-complexity flaw of equal CVSS impact. However, for organizations running Cloud Foundry BOSH on Windows in shared or multi-tenant management planes, the PR:N requirement means no authentication barrier exists once adjacency is achieved. SSVC signals: exploitation status unproven, automatable classification unclear due to AC:H, technical impact total if reached. |
| Exploit ScenarioDerived | An attacker with foothold on the Cloud Foundry management network - for example, a compromised internal jump host or a co-tenant in a shared PaaS management segment - sends a crafted input to the BOSH CLI process running on a Windows operator workstation. The CLI passes the input to a PowerShell execution context without sanitizing shell metacharacters, causing the injected command to execute with the privileges of the BOSH CLI process. No public exploit code has been identified at time of analysis, but PowerShell injection patterns are well-documented and could be adapted by an attacker familiar with the BOSH CLI's command processing logic. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 21, 2026
Command injection in Cloud Foundry's BOSH CLI on Windows enables an adjacent-network attacker to execute arbitrary shell commands - specifically via PowerShell injection - without requiring authentication. The vulnerability affects all tracked versions of the BOSH CLI (cpe:2.3:a:cloud_foundry_foundation:bosh_cli) when deployed on Windows hosts, resulting in full confidentiality, integrity, and availability compromise of the affected system. No public exploit code or CISA KEV listing has been identified at time of analysis, but the high-impact CVSS vector (7.5) and the specificity of the PowerShell injection vector indicate meaningful risk for Cloud Foundry operators running BOSH on Windows.
RemediationAI
Consult the Cloud Foundry Foundation vendor advisory at https://www.cloudfoundry.org/blog/cve-2026-47827-bosh-cli-powershell-injection/ for the official patched BOSH CLI release version, as no specific fix version was confirmed from the data available at time of analysis. As an immediate compensating control, migrate BOSH CLI operations from Windows to Linux-based jump hosts where PowerShell injection surfaces do not apply - this eliminates the vulnerable code path entirely and has no functional trade-off in environments where Linux is available. If Windows BOSH hosts cannot be migrated, restrict management network access to the BOSH Director plane using firewall or network segmentation rules, reducing the pool of adjacent-network positions an attacker could exploit (mitigates AV:A reach, does not eliminate the flaw). Additionally, avoid passing untrusted or externally-sourced strings to BOSH CLI commands on Windows until a patch is applied. No patch version should be assumed from this analysis - verify the exact fixed release directly from the vendor advisory before upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BOSH is Cloud Foundry's infrastructure orchestration CLI, used to manage deployment manifests, director connections, and release lifecycle operations in enterprise PaaS environments. On Windows, the CLI invokes PowerShell for system-level operations, creating a classic injection surface when user-supplied or network-supplied input is passed to shell execution contexts without proper sanitization or escaping. CWE data is absent from this entry, but the described behavior maps to CWE-78 (OS Command Injection) or CWE-88 (Argument Injection to a CLI), common in tools that construct shell command strings dynamically. The CPE wildcard (cpe:2.3:a:cloud_foundry_foundation:bosh_cli:*:*:*:*:*:*:*:*) indicates no bounded affected version range has been confirmed - all BOSH CLI versions on Windows are implicitly in scope. The adjacent network attack vector (AV:A) is consistent with BOSH's typical deployment pattern, where the CLI communicates with a BOSH Director over internal PaaS management networks rather than the public internet.
Know when Bosh Cli gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Adjacent vector confirmed by BOSH's internal-network deployment model; AC:H reflects unspecified but required triggering conditions; PR:N as no auth barrier exists once adjacent.
Primary rating from Vendor (vmware).
CVSS VectorVendor: vmware
Lifecycle Timeline
2DescriptionCVE.org
Command Injection in BOSH CLI tool on windows in Cloud Foundry allows a remote attacker to execute arbitrary shell commands via command injection vulnerabilities
Executive ViewAI
Cloud Foundry BOSH CLI deployments on Windows are vulnerable to unauthenticated command injection from adjacent network attackers, enabling complete system compromise. No vendor patch is currently available, creating immediate risk for organizations operating Cloud Foundry infrastructure on Windows systems. Urgent network isolation and monitoring are required to contain exposure.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict BOSH CLI network access to isolated, segmented networks with strict ingress rules from adjacent networks; (2) enforce Windows Firewall policies limiting inbound access to authorized administrative hosts only; (3) deploy EDR/XDR monitoring for PowerShell command injection detection; (4) enforce PowerShell execution policies and enable comprehensive PowerShell logging and transcription; (5) consider relocating BOSH CLI operations to non-Windows systems or air-gapped network topologies until patches become available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Man-in-the-middle credential theft and root code execution affects the BOSH CLI (bosh-cli) prior to v7.10.4, which fails
Cloud Foundry BOSH CLI, versions prior to v3.0.1, contains an improper access control vulnerability. Rated high severity
Argument injection in bosh-cli versions before v7.10.4 lets a compromised or malicious BOSH Director inject arbitrary Op
Arbitrary command execution on operator workstations in Cloud Foundry BOSH CLI before 7.10.5 allows a compromised or mal
EUVD-2026-63874
GHSA-p279-35hc-hx5p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB