# CVE-2026-41013: Tenant-controlled comma smuggles arbitrary CIFS mount options

> A low-privileged CloudFoundry space developer can inject arbitrary CIFS mount options to escalate privileges and bypass security controls on Diego cells.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-8h76-qw8h-fmjh

## What is CVE-2026-41013?

CVE-2026-41013 is a high-severity command injection vulnerability in CloudFoundry Foundation CF Deployment, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-41013?


## How do I fix CVE-2026-41013?

No fix has been published for CVE-2026-41013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41013 being exploited?

There is no known exploitation of CVE-2026-41013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41013 and fix it if it is affected.

What it is: CVE-2026-41013 is a high-severity command injection vulnerability in CloudFoundry Foundation CF Deployment, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41013 in the wild and no public exploit code.

Affected product: CloudFoundry Foundation CF Deployment. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41013/ (Markdown: https://insights.sbomify.com/CVE-2026-41013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41013
- OSV: https://osv.dev/vulnerability/CVE-2026-41013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41013/
Summaries are generated and may contain mistakes; the official description above is the record.