What is the CVSS score of CVE-2026-47187?

CVE-2026-47187 has a CVSS 3.1 base score of 9.3 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of sshfs are affected by CVE-2026-47187?

libfuse sshfs versions 3.7.5 and earlier fail to validate symlink targets when mounting remote filesystems, allowing a malicious or compromised SSH server to redirect the client to read or write…. A patch is available.

How to fix or mitigate CVE-2026-47187?

Within 24 hours, identify and catalog all systems running sshfs, determine affected version numbers, and immediately suspend sshfs access to non-critical or external SSH servers; document current mount points and usage patterns. Within 7 days, enforce organization-wide policy restricting sshfs mounts exclusively to explicitly whitelisted, internally-managed SSH servers, mandate SSH key-based authentication, and deploy enhanced logging on all sshfs-connected systems. Within 30 days, deploy sshfs 3.7.6 (or later) across all affected systems upon vendor release and verify successful patch application with version confirmation.

sshfs CVE-2026-47187

EUVD-2026-62493 CRITICAL

Improper Link Resolution Before File Access (CWE-59)

2026-05-30

Denial Of Service Apache Path Traversal

9.3

CVSS 3.1 · Vendor

Severity by source

Vendor (CNA) PRIMARY

9.3 CRITICAL

AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

vuln.today AI

9.3 CRITICAL

Malicious remote server needs no client privileges (PR:N, AV:N, AC:L) but the user must mount it and traverse the link (UI:R); escaping the mount to the local filesystem is a scope change (S:C) enabling local read/write (C:H/I:H, A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

SUSE

CRITICAL

qualitative

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

Aug 19, 2026 - 16:17 EUVD

Source Code Evidence Fetched

Aug 19, 2026 - 15:23 vuln.today

Analysis Generated

Aug 19, 2026 - 15:23 vuln.today

CVSS changed

Aug 19, 2026 - 15:22 NVD

9.3 (CRITICAL)

CVE Published

May 30, 2026 - 12:45 oss-security

CRITICAL 9.3

CVE Published

May 30, 2026 - 12:45 nvd

UNKNOWN (no severity yet)

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

AnalysisAI

Symlink-based mount escape in libfuse sshfs 3.7.5 and earlier lets a malicious or compromised SSH server craft symlink targets (absolute paths or targets containing '..') that the sshfs client passes unchecked to the local kernel, enabling local file reads and writes outside the intended mount root when the mounting user traverses them. Rated CVSS 9.3 (scope-changed) and tracked as a link-following flaw (CWE-59); no public exploit identified at time of analysis, and EPSS is very low at 0.03% (10th percentile). The fix introduces default symlink containment shipped in sshfs 3.7.6.

Technical ContextAI

sshfs is a FUSE-based filesystem that mounts a remote directory over SFTP/SSH; all metadata, including symlink targets returned by SFTP READLINK, is supplied by the remote server and exposed to the local kernel. The vulnerability is a CWE-59 link-following issue: prior to the fix, sshfs_readlink relayed server-supplied symlink targets verbatim, so a server could return absolute targets (e.g. /etc/passwd) or targets containing '..' components that resolve outside the mount root. Because the server is untrusted and controls intermediate path components, lexical normalization cannot be trusted; the upstream fix (commit bcd132f, PR 361) adds symlink_target_is_contained(), rejecting absolute or '..'-containing targets with EPERM under a new default-on 'contain_symlinks' option.

RemediationAI

Vendor-released patch: upgrade to sshfs 3.7.6 or later (https://github.com/libfuse/sshfs/releases/tag/sshfs-3.7.6), which enables symlink containment by default so absolute and '..'-containing symlink targets from the server are rejected with EPERM. If you cannot upgrade immediately, the primary compensating control is to only mount SSH servers you fully trust and control, since the attack requires a malicious or compromised server; avoid mounting untrusted or third-party endpoints. After upgrading, keep the default 'contain_symlinks' enabled and do not pass 'no_contain_symlinks'; note that combining 'transform_symlinks' with containment can cause legitimate transformed links containing '..' to be rejected, so review that interaction (the tool emits a warning). Consult GHSA-pjv6-2c3f-r357 (https://github.com/libfuse/sshfs/security/advisories/GHSA-pjv6-2c3f-r357) for full guidance.