EUVD-2026-62494Severity by source
AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Local vector (AV:L) and active user interaction (UI:R) are required; no privileges needed (PR:N) to invoke sshfs; high complexity (AC:H) because attacker must control the mount source argument through an indirect channel.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
6Description PRE-NVD
AnalysisAI
SSH argument injection in sshfs 3.7.5 and earlier allows a locally-present attacker to inject arbitrary SSH client options by supplying a dash-prefixed hostname such as '-oProxyCommand=id' as the remote filesystem mount source. When a user is induced to mount a crafted sshfs URI, the parsed hostname is passed directly to the underlying SSH subprocess without a preceding '--' argument separator or leading-dash validation, causing SSH to interpret the hostname as an option flag and execute the injected command at the victim user's privilege level. No public exploit has been identified at time of analysis, though the oss-security disclosure (2026-05-30) and a released fix at sshfs-3.7.6 confirm the issue; EPSS is 0.02% (6th percentile) with no CISA KEV listing.
Technical ContextAI
sshfs (libfuse/sshfs) is a FUSE-based userspace filesystem client that mounts remote directories over SFTP by spawning an SSH subprocess. The vulnerability is classified CWE-88 (Argument Injection or Modification): prior to the patch, the hostname component parsed from the mount source argument was appended to the SSH argument vector without a preceding '--' end-of-options separator and without validating that it did not begin with a dash. Because SSH treats any leading-dash positional argument as an option flag, a crafted hostname such as '-oProxyCommand=/usr/bin/id' is interpreted by the SSH client as a ProxyCommand directive rather than a remote host, enabling arbitrary command execution. The fix in commit 29bb565ea6405e2dd5a0ea65fe64da117e76055e closes the issue by (1) inserting '--' before the hostname argument in the SSH invocation and (2) explicitly rejecting hostnames starting with '-' with an 'invalid hostname' error and non-zero exit. The 'Apache' tag co-appearing in the oss-security thread data bleeds over from CVE-2026-48827 (Apache MINA SSHD) reported in the same thread and does not apply to this issue.
RemediationAI
Upgrade sshfs to version 3.7.6, the confirmed patched release available at https://github.com/libfuse/sshfs/releases/tag/sshfs-3.7.6. This release incorporates commit 29bb565ea6405e2dd5a0ea65fe64da117e76055e, which both inserts a '--' separator before the hostname argument in the SSH subprocess call and explicitly rejects hostnames beginning with a dash. For users who cannot immediately upgrade, a practical compensating control is to validate any sshfs mount source in wrapper scripts using a pattern such as rejecting strings matching '^-' - this blocks the injection vector without an upgrade but does not cover library-level or programmatic callers of sshfs. Environments using sshfs in CI/CD pipelines or shared tooling should audit whether the mount source can be influenced by external input and restrict it to operator-controlled values. Full advisory details are at https://github.com/libfuse/sshfs/security/advisories/GHSA-mm85-q63v-4476.
Same technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today