VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

SSH.NET: vulnerability history, versions and safety

SSH.NET is a package in the NuGet ecosystem. Vulert records 3 vulnerabilities for it across 32 releases, from Jun 2022 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 17 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all SSH.NET vulnerabilities

Vulert verdict on SSH.NET 2026.0.0 i

Updated on 23 Oct 2026

Good news: 2026.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2026.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2026.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2026.0.0 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 2 in the last year i
  • Latest disclosure 17 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 4,385 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for SSH.NET, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2026.0.0 09 Aug 2026 none MIT — Details →
2025.1.0 27 Oct 2025 H2 MIT Yes Details →
2025.0.0 18 Apr 2025 H2 MIT Yes Details →
2024.2.0 12 Nov 2024 H2 MIT Yes Details →
2024.1.0 01 Jul 2024 H2 MIT Yes Details →
2024.0.0 21 Feb 2024 H2 MIT Yes Details →
2023.0.1 29 Dec 2023 H2 MIT Yes Details →
2023.0.0 10 Oct 2023 H2 MIT Yes Details →
2020.0.2 29 May 2022 H2 non-standard Yes Details →
2020.0.1 24 Jan 2021 H2 M1 non-standard Yes Details →
2020.0.0 31 Dec 2020 H2 M1 non-standard Yes Details →
2020.0.0-beta1 07 Jun 2020 H2 M1 non-standard Yes Details →
2016.1.0 16 Oct 2017 H2 M1 non-standard Yes Details →
2016.1.0-beta4 07 Oct 2017 H2 M1 non-standard Yes Details →
2016.1.0-beta3 20 Sep 2017 H2 M1 non-standard Yes Details →
2016.1.0-beta2 16 Aug 2017 H2 M1 non-standard Yes Details →
2016.1.0-beta1 14 Dec 2016 H2 M1 non-standard Yes Details →
2016.0.0 02 Aug 2016 H2 M1 non-standard Yes Details →
2016.0.0-beta3 27 Jul 2016 H2 M1 non-standard Yes Details →
2016.0.0-beta2 25 Jun 2016 H2 M1 non-standard Yes Details →
2016.0.0-beta1 19 Jun 2016 H2 M1 non-standard Yes Details →
2014.4.6-beta2 22 Nov 2014 H2 M1 non-standard Yes Details →
2014.4.6-beta1 06 Apr 2014 H2 M1 non-standard Yes Details →
2013.4.7 06 Apr 2013 H2 M1 non-standard Yes Details →
2013.1.27 27 Jan 2013 H2 M1 non-standard Yes Details →
2013.1.8 08 Jan 2013 H2 M1 non-standard Yes Details →
2012.21.12 21 Dec 2012 H2 M1 non-standard Yes Details →
2012.20.12 20 Dec 2012 H2 M1 non-standard Yes Details →
2012.12.3 04 Dec 2012 H2 M1 non-standard Yes Details →
2012.3.9 09 Mar 2012 H2 M1 non-standard Yes Details →
2011.12.7 03 Mar 2012 H2 M1 non-standard Yes Details →
2011.9.28 13 Oct 2011 H2 M1 non-standard Yes Details →
2011.7.29 16 Sep 2011 H2 M1 non-standard Yes Details →

All 33 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for SSH.NET

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-85756: SSH.NET ScpClient Remote Command Execution Vulnerability 7.5 high 2026.0.0 17 Sep 2026
CVE-2026-48798: SSH.NET ScpClient Recursive Download Vulnerability Leading to Arbitrary File Write 7.1 high 2026.0.0 12 Aug 2026
CVE-2022-29245: Weak private key generation in SSH.NET 6.5 medium 2020.0.2 01 Jun 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About SSH.NET

Is SSH.NET safe to use?

Vulert records 3 vulnerabilities for SSH.NET in NuGet: 0 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is SSH.NET's Vulert package health score?

Vulert scores SSH.NET 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of SSH.NET affected?

No. 2026.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of SSH.NET should I use?

2026.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does SSH.NET have?

3 vulnerabilities are recorded for SSH.NET in the NuGet ecosystem: 0 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new SSH.NET vulnerabilities disclosed?

2 vulnerabilities were recorded for SSH.NET in the last 12 months, and the oldest entry in this database dates to 01 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of SSH.NET are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor SSH.NET for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the SSH.NET version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.