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

> A rogue SFTP server can exploit symlink handling in SSHFS to read or write arbitrary local files on the client system.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** ALPINE-CVE-2026-47187, AZL-97011, DEBIAN-CVE-2026-47187, GHSA-pjv6-2c3f-r357, UBUNTU-CVE-2026-47187

## What is CVE-2026-47187?

CVE-2026-47187 is a critical path traversal vulnerability in libfuse sshfs, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

Upgrade to a fixed version.

## Is CVE-2026-47187 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47187 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47187 is a critical path traversal vulnerability in libfuse sshfs, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47187 exists.

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

## Sources

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

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