CVE-2026-47187

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
58(Track*)
EG Risk 58/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Symlink Escape: Rogue SFTP Server → Local File Read/Write · Advisory · libfuse/sshfs · GitHub

https://github.com/libfuse/sshfs/security/advisories/GHSA-pjv6-2c3f-r357
github_release Patch Available

SSHFS 3.7.6

Patch available: libfuse/sshfs sshfs-3.7.6

https://github.com/libfuse/sshfs/releases/tag/sshfs-3.7.6
github_pr Patch Available

add contain_symlinks option to prevent symlink escape attacks

Patch available: libfuse/sshfs sshfs-3.7.6 (PR #361 merged 2026-05-29)

https://github.com/libfuse/sshfs/pull/361
github_commit Patch Available

commit bcd132f17ccf (libfuse/sshfs)

Patch available: libfuse/sshfs sshfs-3.7.6 (contains commit bcd132f17ccf)

https://github.com/libfuse/sshfs/commit/bcd132f17ccf1b8592a229df797c9b08883fec26

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
sshfs—3.7.6-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
sshfs—3.7.6-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
sshfs—3.7.6-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
sshfs—3.7.6-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
sshfs—3.7.6-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
sshfs-fuse3.7.3-1.13.7.3-1.2~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sshfs-fuse3.7.3-1.1, 3.7.3-1.2~deb12u13.7.3-1.2~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sshfs-fuse3.7.3-1.1, 3.7.3-1.2~deb12u1, 3.7.3-1.2~deb13u13.7.3-1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 18:33 UTCEG score recompute
  2. 2026-09-18 21:52 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 21:33 UTCEG score recompute
  5. 2026-09-16 14:35 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 09:51 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 04:04 UTCEG score recompute
  10. 2026-09-13 18:13 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 17:52 UTCEG score recompute
  13. 2026-09-12 15:01 UTCEPSS rescore
  14. 2026-09-11 17:34 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 13:00 UTCEG score recompute
  17. 2026-09-11 09:37 UTCEPSS rescore
  18. 2026-09-10 12:20 UTCEG score recompute
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-09 02:38 UTCEG score recompute
  21. 2026-09-08 22:00 UTCEPSS rescore
  22. 2026-09-07 19:46 UTCEG score recompute
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 16:36 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 37 more
  1. 2026-09-05 16:12 UTCEG score recompute
  2. 2026-09-04 15:37 UTCEG score recompute
  3. 2026-09-04 07:20 UTCEG score recompute
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 21:19 UTCEG score recompute
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 17:16 UTCEG score recompute
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 08:20 UTCEG score recompute
  10. 2026-08-30 23:19 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 02:59 UTCEG score recompute
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-29 01:57 UTCEG score recompute
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:57 UTCEG score recompute
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 18:12 UTCEG score recompute
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 17:20 UTCEG score recompute
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 17:02 UTCEG score recompute
  23. 2026-08-24 12:37 UTCEG score recompute
  24. 2026-08-23 04:08 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 03:47 UTCEG score recompute
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-20 23:21 UTCEG score recompute
  29. 2026-08-20 22:55 UTCEPSS rescore
  30. 2026-08-20 19:18 UTCEG score recompute
  31. 2026-08-20 18:32 UTCEG score recompute
  32. 2026-08-20 08:23 UTCEG score recompute
  33. 2026-08-20 04:19 UTCEG score recompute
  34. 2026-08-20 04:08 UTCEG score recompute
  35. 2026-08-19 15:24 UTCEG score recompute
  36. 2026-08-19 14:57 UTCEG score recompute
  37. 2026-08-19 14:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47187?
CVE-2026-47187 is a critical vulnerability published on August 19, 2026. 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…
When was CVE-2026-47187 disclosed?
CVE-2026-47187 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47187 actively exploited?
CVE-2026-47187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all scored CVEs.
What is the CVSS score of CVE-2026-47187?
CVE-2026-47187 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-47187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47187, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47187

Explore →

Is Your Infrastructure Affected by CVE-2026-47187?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs