Loading story…
A critical flaw tracked as CVE-2026-47187 affects SSHFS versions earlier than 3.7.6, allowing a malicious or rogue SFTP server to trigger local file read or write on a client system through crafted symlinks. The issue stems from SSHFS passing absolute symlink targets or relative targets containing .. traversal components through FUSE, after which the local kernel VFS can resolve those paths outside the mounted filesystem. If a user or client-side tool such as cp, rsync, backup software, or an editor follows the link, local readable files can be exposed or attacker-controlled data can be written into writable local files, including startup or scheduled-task locations.
The fix was merged into libfuse/sshfs as a new contain_symlinks protection that is enabled by default and rejects absolute symlink targets and any target containing .., returning EPERM. Maintainers described the approach as intentionally strict and lexical because an adversarial filesystem can manipulate intermediate path components, making depth-based checks unreliable. The update also adds a no_contain_symlinks opt-out for trusted legacy environments, updates documentation, and includes tests covering blocked traversal attempts, safe symlinks, option precedence, and interactions with transform_symlinks.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
On August 19, 2026, CVE-2026-47187 was published for an SSHFS vulnerability affecting versions earlier than 3.7.6 that lets a rogue SFTP server induce local file read or write via malicious symlink targets. The CVE entry states the issue is fixed in SSHFS 3.7.6 and references the fixing commit and pull request.
On May 29, 2026, libfuse/sshfs merged a change adding the contain_symlinks option, enabled by default, to block absolute symlink targets and targets containing '..' in order to prevent symlink escape attacks from malicious SFTP servers. The merge completed in pull request #361 and the associated branch was deleted the same day.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two vulnerabilities in **sshfs** were disclosed and fixed in version **3.7.6**, affecting versions up to **3.7.5**. The more severe issue, **CVE-2026-47187**, is a symlink escape flaw that lets a rogue SFTP server trick the client into reading from or writing to unintended paths on the local filesystem by returning unsafe symlink targets. The second bug, **CVE-2026-48711**, is an argument injection weakness in hostname parsing that can turn a crafted mount source into an SSH option, enabling arbitrary local command execution under specific conditions and, in some cases, without requiring SSH authentication. Public technical details and exploit code have now been released, raising the risk of active abuse against systems that use sshfs to mount remote directories over SFTP. The flaws were privately reported by Abhinav Agarwal and addressed through a coordinated release, but defenders are being urged to upgrade immediately to **sshfs 3.7.6 or later** and verify trusted remote server keys, as a malicious or spoofed server could otherwise trigger client-side compromise.
Aug 19, 2026
Multiple vulnerabilities in **libssh2** have exposed SSH clients and products that embed the library to attacks from malicious or impersonated SSH servers. The most severe issue, **`CVE-2026-55200`**, is a pre-authentication out-of-bounds heap write in `ssh2_transport_read()` that affects all versions through **1.11.1** and could allow remote code execution, while **`CVE-2026-55199`** can force clients into a CPU-intensive loop during key exchange and cause denial of service. The library is widely used in **curl**, backup software, IoT firmware, and network appliances, raising broad supply-chain risk, especially where libssh2 is statically linked or bundled into downstream products. A separate flaw, **`CVE-2025-15661`**, affects `sftp_symlink()` in `src/sftp.c` and can be triggered during SFTP `READLINK` or `REALPATH` operations when a malicious server or man-in-the-middle sends a crafted `SSH_FXP_NAME` response with an oversized `link_len` value. That bug causes a heap buffer over-read that may disclose memory contents or crash applications. Fixes were reported in commits **`97acf3d`**, **`1762685`**, and **`2dae302`**, but at the time of reporting no official libssh2 release containing the newer patches had been published, leaving downstream vendors responsible for shipping their own updates.
Jul 12, 2026
A flaw in the Linux kernel FUSE subsystem, tracked as **`CVE-2026-31694`**, allows a local attacker to escalate privileges to root by exploiting how cached directory entries are handled during `readdir` operations. The bug is in `fuse_add_dirent_to_cache()`, where an attacker-controlled serialized FUSE directory entry can be copied into a single 4 KiB cache page without verifying that the entry itself fits, causing a **24-byte overflow** and adjacent memory corruption on affected systems. Reports say a malicious FUSE server can trigger the issue through oversized filename data returned to the kernel. Researchers demonstrated exploitation by corrupting cached bytes associated with a SUID binary such as **`/usr/bin/su`**, including a proof of concept that modified the cached `.init` page on Ubuntu 26.04 to execute code that calls `setuid(0)` and `setgid(0)` before spawning a root shell. The vulnerable logic was introduced in 2018, but practical exploitation reportedly became reachable with Linux `v6.16-rc1` after a 2025 increase to the `readdir` buffer size. An upstream patch has been accepted to reject directory entries whose serialized size exceeds `PAGE_SIZE` before caching, while interim mitigations include limiting FUSE use, removing the SUID bit from `fusermount3` where unnecessary, and restricting unprivileged user namespaces.
Aug 20, 2026