External risk intelligence

SSHFS Path Traversal Vulnerability Allows Local File Disclosure and Modification.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-47187

SSHFS is a client-side utility used to mount remote filesystems. While it involves network communication, it is typically initiated by a local user or automated script in a specific, intentional connection to a known server, rather than operating as an internet-facing service or listener.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability in SSHFS, a tool for connecting to SSH servers, could allow a malicious server to access or modify local files on a connected client. This occurs when SSHFS improperly handles symbolic links returned by the server, potentially leading to the disclosure of sensitive local data or the injection of unauthorized content. The main concern is confirming relevance and exposure to determine if your environment is impacted.

Malicious servers can read or write local files.
Critical for any use of SSHFS to connect remote files.
Verify if your organization uses SSHFS and assess risk.

Attack Path

How an attacker could exploit the issue

An attacker, controlling an SFTP server, can trick an SSHFS client into resolving symbolic links on the local filesystem. This occurs when the SFTP server provides specially crafted absolute or relative symlink targets. When the SSHFS client processes these, it can be tricked into reading or writing local files, potentially leading to sensitive information disclosure or unauthorized modification of system files.

Entry condition: Attacker controls SFTP server.
Trigger point: SSHFS client follows crafted symlinks.
Resulting risk: Local file disclosure or modification.

Live Threat

Current exploitation, exposure, and threat context

A malicious SFTP server could trick an SSHFS client into revealing readable local files or overwriting local files. This could happen when the SSHFS client follows symbolic links, which are manipulated by the server to point to local file paths. The disclosure or modification of files could occur through common operations like copying, syncing, or editing files.

Local files and system configurations at risk.
Server-controlled symlinks could be followed.
Disclosure or modification of local file content.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

The real-world ownership for this vulnerability lies with teams managing systems that utilize SSHFS for mounting remote file systems. The initial focus should be on identifying all instances of SSHFS, assessing their exposure and business criticality, and then coordinating with the accountable owners for remediation.

Owns the issue: System owners and infrastructure teams.
Verify first: Identify SSHFS deployments and reachability.
Action: Plan remediation based on risk assessment.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is SSHFS and how is it used?

SSHFS is a client-side utility that lets users mount remote directories over an SSH connection as if they were local folders. It relies on the FUSE (Filesystem in Userspace) interface to allow the client computer's kernel to interact with the remote filesystem. Developers and administrators commonly use it to securely access or synchronize files stored on remote servers through standard system commands.

What does CWE-59 mean for CVE-2026-47187?

CWE-59 refers to improper link resolution before file access. In this CVE, the SSHFS client fails to properly validate symbolic links provided by a remote SFTP server. Because the software does not securely restrict these paths, it may resolve them against the local filesystem instead of the remote one, effectively treating a remote path as a local file location.

How does an attacker trigger this vulnerability?

An attacker must control the SFTP server to which your client connects. They provide a malicious symlink pointing to sensitive locations on your machine. Simply connecting to a server does not trigger the bug; the vulnerability occurs when the SSHFS client attempts to follow or resolve these manipulated links during file operations like copying or backing up data.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal labels the risk as Unlikely. Because SSHFS is a client-side tool typically used for specific, intentional connections to known servers rather than acting as an internet-facing listener, it does not share the same exposure profile as a public service. You are primarily at risk only if you connect to a compromised or malicious remote server.

How do I address this SSHFS vulnerability?

The primary response is to update your SSHFS software to version 3.7.6 or later, which contains the fix for the symlink validation logic. If updating is not immediately possible, audit your current SSHFS connections to ensure you are only mounting filesystems from trusted sources. Prioritize systems that perform automated file operations, as these are most likely to follow malicious links without human oversight.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.