If a client application uses ScpClient.Download to pull a directory from an untrusted or compromised server, the library will construct local file paths based on these unsanitized names. This allows the attacker to write files outside of the intended target directory, potentially overwriting sensitive files such as SSH authorized keys, user profile startup scripts (e.g., .bashrc, .profile), or application configuration files. This vulnerability effectively grants the attacker the ability to perform operations with the privileges of the user running the .NET application. The issue was addressed in the project's commit history, and users are advised to upgrade to the latest version to prevent malicious path traversal during SCP operations.

Impact

The impact of this vulnerability is significant, as it enables arbitrary file write capabilities on the host running the application. Successful exploitation could lead to privilege escalation or remote code execution by overwriting critical system or user files (e.g., ~/.ssh/authorized_keys, ~/.bashrc, or cron jobs). The threat specifically targets environments where automated, recurring backups or data synchronization tasks are performed using SSH.NET against untrusted or potentially compromised remote infrastructure.

Recommendation

• Upgrade the SSH.NET NuGet package to the latest version that includes the fix for CVE-2026-48798.
• Audit all applications utilizing SSH.NET to determine if ScpClient.Download is used to sync data from external, non-hardened SCP servers.
• Review application-level access controls for the user account executing the SSH.NET library to minimize the impact of a potential write primitive (adhere to principle of least privilege).
• Monitor logs for unusual directory creation or file write events initiated by .NET applications performing network synchronization tasks.