Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain CF space-developer role
-
DeliveryCreate or bind SMB volume service instance
-
ExploitInject comma-smuggled CIFS options past allowlist
-
ExecutionDiego mounts share with attacker-controlled kernel options
-
PersistEscalate privileges on shared Diego cell
-
ImpactBypass tenant isolation and access other tenants' data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Argument sanitization
|
| Exploitation Conditions | Requires (1) a Cloud Foundry foundation running smb-volume-release < v3.60.0 or CF Deployment < v56.0.0 with the smb-volume service broker registered and enabled in the marketplace, (2) at least one Diego cell configured to accept SMB volume mounts, and (3) attacker possession of CF space-developer privileges in any org/space permitted to create or bind SMB volume service instances. Exploitation is limited where SMB volume services are not deployed, where the smb-volume broker is restricted from tenant spaces, or where the foundation is single-tenant such that kernel mount-option injection does not cross a trust boundary; no end-user interaction is required, but the attacker must already hold a valid CF account with developer-level role on a space that can request SMB binds. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N indicates a network-reachable, low-complexity attack that requires only a CF space-developer role - a role routinely granted to many internal users in shared CF foundations - and yields high confidentiality and integrity impact with no availability impact and unchanged scope. Note that despite S:U, the practical effect described by the vendor (kernel mount-option control on a shared Diego cell) materially affects other tenants on the same cell, so real-world blast radius likely exceeds the 'scope unchanged' label; defenders should weigh that contradiction. EPSS is not provided, the CVE is not in CISA KEV, and no public PoC is referenced, so this is best treated as a credible insider/abuse-of-low-privilege risk in multi-tenant CF deployments rather than mass-exploited; the combination of low privilege requirement, a sole authoritative vendor advisory, and a clear argument-injection primitive still warrants prompt patching in any shared foundation. |
| Exploit ScenarioDerived | A CF user with the space-developer role in any space on a multi-tenant foundation creates or binds an SMB volume service instance, supplying a mount-option value that embeds an extra comma-separated CIFS flag (for example, smuggling uid=0 or a credentials path) past the allowlist. When Diego mounts the share into a tenant container, the kernel CIFS client honors the smuggled options, giving the attacker effective privilege escalation and the ability to bypass tenant isolation controls on that cell. No public PoC is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 01, 2026
Privilege escalation in Cloud Foundry smb-volume-release (prior to v3.60.0) and CF Deployment (prior to v56.0.0) lets a low-privileged CF space developer smuggle arbitrary CIFS mount options past the mount-option allowlist, gaining kernel-level mount control on shared Diego cells. The flaw maps to CWE-88 (argument injection) and carries CVSS 8.1 with low-privilege network exploitation; no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
Apply the vendor-released patches: upgrade smb-volume-release to v3.60.0 or later and CF Deployment to v56.0.0 or later, per the Cloud Foundry advisory at https://www.cloudfoundry.org/blog/cve-2026-41013-tenant-controlled-comma-smuggles-arbitrary-cifs-mount-options/. Where immediate upgrade is not possible, operators can disable SMB volume services on affected Diego cells (removing the smb-volume broker from the marketplace) to eliminate the attack surface entirely, at the cost of breaking workloads that legitimately bind SMB shares; alternatively, restrict who can create or bind SMB volume service instances by tightening space-developer assignments and using org/space quotas to limit which spaces can request SMB binds, accepting that this reduces self-service but preserves SMB functionality for trusted spaces. Audit existing SMB service bindings for suspicious mount-option values (especially strings containing embedded commas, uid=, gid=, file_mode=, dir_mode=, or credentials=) before patching to detect prior abuse.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Cloud Foundry's Diego runtime delegates SMB/CIFS volume mounts to a broker that builds kernel mount commands from user-supplied parameters. The smb-volume-release component enforces an allowlist of mount options to keep tenants from passing dangerous kernel CIFS flags (e.g., uid/gid/file_mode, credentials path). Per the Cloud Foundry advisory titled 'Tenant-controlled comma smuggles arbitrary CIFS mount options,' the parser splits and validates options but does not normalize embedded commas, allowing a tenant value to smuggle additional comma-separated options through the allowlist. This is the canonical CWE-88 'Improper Neutralization of Argument Delimiters' pattern, where the boundary between data and argument is not preserved end-to-end across the broker, garden-runc, and the kernel CIFS client on multi-tenant Diego cells (CPE: cloudfoundry_foundation:smb-volume-release and cloudfoundry_foundation:cf_deployment).
Know when Cf Deployment 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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (vmware) · only source for this CVE.
CVSS VectorVendor: vmware
Lifecycle Timeline
3DescriptionCVE.org
Input validation bypass in SMB volume mount handling in CloudFoundry Foundation diego-release allows low-privileged CF space developer to inject arbitrary kernel CIFS mount options via bypassing the mount-option allowlist, enabling privilege escalation and security control bypass on multi-tenant Diego cells.
Affected versions: smb-volume-release: All versions prior to v3.60.0 CF Deployment: All versions prior to v56.0.0
Executive ViewAI
Cloud Foundry deployments using smb-volume-release and CF Deployment are vulnerable to privilege escalation attacks where low-privileged developers can bypass security controls and gain unauthorized kernel-level mount access on shared infrastructure. This affects multi-tenant environments and could enable lateral movement, unauthorized data access, or service disruption across Diego cells. Organizations running affected versions require immediate patching to restore security boundaries between tenant workloads.
Apply vendor patch.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Cf Deployment
View allPrivate key disclosure in Cloud Foundry UAA versions v76.12.0 through v78.12.0 allows unauthenticated remote attackers t
Cloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fet
Adversary-in-the-middle credential theft and privilege escalation affects Cloud Foundry UAA (User Account and Authentica
Privilege escalation in Cloud Foundry UAA (User Account and Authentication server) lets users who authenticate via a fed
Authentication bypass in Cloud Foundry UAA (User Account and Authentication) versions 2.0.0 through 78.13.0 allows remot
Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also t
In Cloud Foundry UAA, versions prior to 74.14.0, a CSRF vulnerability exists due to the OAuth2 state parameter not being
Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. Rated high s
Cloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability. Rated high severity
In Cloud Controller versions prior to 1.46.0, cf-deployment versions prior to 1.3.0, and cf-release versions prior to 28
Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input. Rated high severity (CVSS 8.
Cloud foundry instances having CAPI version between 1.140 and 1.152.0 along with loggregator-agent v7+ may override othe
EUVD-2026-33727
GHSA-8h76-qw8h-fmjh
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB