LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47187: SSHFS Symlink Escape: Rogue SFTP Server → Local File Read/Write

SSHFS is a network filesystem client for connecting to SSH servers. Prior to version 3.7.6, a rogue SFTP server can return absolute symlink targets or relative targets containing parent-directory components that SSHFS passes through FUSE for resolution by the client kernel against the local filesystem. The documented transform_symlinks mitigation does not contain relative targets because transform_symlink() returns early at sshfs.c:2181, while sshfs_readlink() at sshfs.c:2234 to sshfs.c:2236 otherwise copies the server-supplied link target to the kernel. A victim or victim-side tool that follows such a link through ordinary operations such as cp, rsync, backup tooling, or an editor can disclose readable local files back to the server or write server-controlled content to writable local files, potentially including startup or scheduled-task files. This issue is fixed in version 3.7.6.

CriticalCVSS 9.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

SSHFS versions before 3.7.6 can let a malicious SFTP server create links that reach outside the mounted filesystem. If a user or automated tool follows one, local files may be disclosed to the server or overwritten. Exploitation requires victim interaction, but routine actions by editors, synchronization, or backup tools may provide it.

Executive priority

Prioritize immediate inventory and upgrade for endpoints mounting third-party, externally managed, or potentially compromised SFTP servers. Treat automated backup and synchronization hosts as especially urgent because routine processing may trigger exposure without deliberate file selection. Where trusted servers are exclusively used, urgency remains high because server compromise would activate the same trust-boundary risk.

Technical view

SSHFS passes attacker-controlled absolute symlink targets, and relative targets containing parent-directory components, through FUSE for local kernel resolution. The documented transform_symlinks option does not contain affected relative targets because transformation returns early. This crosses the remote-mount trust boundary, enabling local confidentiality and integrity impact when a link is followed. Version 3.7.6 fixes the issue.

Likely exposure

Exposure is most likely where SSHFS below 3.7.6 mounts servers that are malicious, compromised, or outside organizational control. Risk increases when users, backup systems, editors, cp, or rsync traverse mounted content. Systems without SSHFS, systems running 3.7.6 or later, and environments never connecting to untrusted SFTP servers are not identified as affected by the supplied evidence.

Exploitation context

The CVSS score is 9.3, with network reachability, low complexity, no server-side privileges, required user interaction, and changed scope. The supplied record does not list this CVE in KEV and provides no evidence of active exploitation. A rogue server must influence symlink targets, and a victim-side process must follow them.

Researcher notes

The supplied advisory attributes the flaw to readlink handling that copies server-provided targets to the kernel, with incomplete protection from transform_symlinks for relative traversal targets. Impact is local file read or write through link-following behavior; availability impact is not claimed. Public exploitation, affected downstream distributions, and forensic indicators are not established in the provided sources.

Mitigation direction

  • Upgrade SSHFS to version 3.7.6 or later.
  • Until upgraded, avoid mounting untrusted or insufficiently controlled SFTP servers.
  • Limit automated tools from traversing affected SSHFS mounts.
  • Review vendor guidance and distribution packages for the corrected release.

Validation and detection

  • Inventory installed SSHFS versions and identify systems below 3.7.6.
  • Identify active SSHFS mounts and assess each server's ownership and trust level.
  • Review backup, synchronization, editor, and file-copy workflows that traverse SSHFS mounts.
  • Confirm upgraded clients report version 3.7.6 or later.
  • Check affected endpoints for unexpected access or modification of sensitive local files.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47187 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N2.85.8GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2026-47187Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libfusesshfs< 3.7.6Listed
Weakness

CWE details

CWE-59

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-59 · source CWE mapping

Improper Link Resolution Before File Access

Improper Link Resolution Before File Access represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs