Is SSH.NET 2013.1 vulnerable?
NuGet · 2 releases from 2013.1.8 to 2013.1.27 · latest SSH.NET is 2026.0.1 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. SSH.NET 2013.1.27, the last 2013.1 release, is affected by 3 known security advisories (2 high, 1 medium), including CVE-2026-85756, CVE-2026-48798, CVE-2022-29245. Upgrade to 2026.0.0 or later to fix all of them.
dotnet add package SSH.NET --version 2026.0.0Is your project on an affected SSH.NET?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting SSH.NET 2013.1.27
SSH.NET: ScpClient allows server-side RCE via default SCP path handling
- Affected
- <2026.0.0
- Fixed in
- 2026.0.0
SSH.NET: ScpClient Recursive Download Allows Arbitrary File Write via Server-Controlled SCP Filenames
- Affected
- <2026.0.0
- Fixed in
- 2026.0.0
Weak private key generation in SSH.NET
- Affected
- <2020.0.2
- Fixed in
- 2020.0.2
Every SSH.NET 2013.1.x release
Affected: 2013.1.8 to 2013.1.27. Latest SSH.NET: 2026.0.1.
| Version | Known advisories |
|---|---|
| SSH.NET 2013.1.27 | CVE-2026-85756, CVE-2026-48798, CVE-2022-29245 |
| SSH.NET 2013.1.8 | CVE-2026-85756, CVE-2026-48798, CVE-2022-29245 |
Which of your client projects are still on SSH.NET 2013.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact SSH.NET version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other SSH.NET versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.