# CVE-2026-60102: Horde VFS < 3.0.1 OS Command Injection via Horde_Vfs_Smb Driver

> Authenticated attackers can execute arbitrary shell commands via malicious filenames in the Horde VFS Smb driver due to insufficient input sanitization.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 8 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-60102, GHSA-4crx-2rrv-xxcf, UBUNTU-CVE-2026-60102

## What is CVE-2026-60102?

CVE-2026-60102 is a high-severity command injection vulnerability in horde Vfs, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Horde Virtual File System (VFS) API before 3.0.1 contains an OS command injection vulnerability in the Horde_Vfs_Smb driver where the _escapeShellCommand() method fails to sanitize command substitution sequences, allowing authenticated attackers to inject arbitrary shell commands through user-controlled filenames. Attackers can supply malicious filenames containing unescaped command substitution payloads through operations such as file upload, folder creation, rename, or deletion, which are interpolated into a double-quoted shell context and executed via proc_open() through /bin/sh -c before smbclient runs, resulting in arbitrary command execution on the underlying system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-60102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60102 is a high-severity command injection vulnerability in horde Vfs, published on 8 Jul 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-60102 in the wild and no public exploit code.

Affected product: horde Vfs. 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-60102/ (Markdown: https://insights.sbomify.com/CVE-2026-60102/index.md)
```

## Sources

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

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