VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

paramiko: vulnerability history, versions and safety

paramiko is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 120 releases, from Jan 2008 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C1 H3 L1 U6
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all paramiko vulnerabilities

Vulert verdict on paramiko 5.1.0 i

Updated on 23 Oct 2026

Careful: 5.1.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.1.0 — affected i
  • Vulnerabilities on record 11 over 18 years · 3 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 3,824 packages i
  • Stars 9,879 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence LGPL-2.1 i

Version list, release dates, licence and dependants published by PyPI, 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 paramiko, 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
5.1.0 18 Oct 2026 L1 U1 LGPL-2.1 No Details →
5.0.1 18 Oct 2026 L1 U1 LGPL-2.1 No Details →
5.0.0 09 May 2026 L1 U1 LGPL-2.1 No Details →
4.0.0 04 Aug 2025 L1 U1 LGPL-2.1 No Details →
3.5.1 04 Feb 2025 L1 U1 non-standard No Details →
3.5.0 15 Sep 2024 L1 U1 non-standard No Details →
3.4.1 11 Aug 2024 L1 U1 non-standard No Details →
3.3.2 11 Aug 2024 L1 U2 non-standard No Details →
3.4.0 18 Dec 2023 L1 U1 non-standard No Details →
3.3.1 28 Jul 2023 L1 U2 non-standard No Details →
3.3.0 28 Jul 2023 L1 U2 non-standard No Details →
3.2.0 25 May 2023 L1 U2 non-standard No Details →
3.1.0 10 Mar 2023 L1 U2 non-standard No Details →
3.0.0 20 Jan 2023 L1 U2 non-standard No Details →
2.12.0 04 Nov 2022 L1 U2 non-standard No Details →
2.11.1 04 Nov 2022 L1 U2 non-standard No Details →
2.10.6 04 Nov 2022 L1 U2 non-standard No Details →
2.11.0 17 May 2022 L1 U2 non-standard No Details →
2.10.5 17 May 2022 L1 U2 non-standard No Details →
2.9.5 17 May 2022 L1 U2 non-standard No Details →
2.10.4 25 Apr 2022 L1 U2 non-standard No Details →
2.9.4 25 Apr 2022 L1 U2 non-standard No Details →
2.10.3 18 Mar 2022 L1 U2 non-standard No Details →
2.9.3 18 Mar 2022 L1 U2 non-standard No Details →
2.10.2 14 Mar 2022 L1 U2 non-standard No Details →
2.10.1 12 Mar 2022 L1 U2 non-standard No Details →
2.10.0 12 Mar 2022 H1 L1 U3 non-standard No Details →
2.9.2 08 Jan 2022 L1 U3 non-standard No Details →
2.9.1 24 Dec 2021 L1 U3 non-standard No Details →
2.9.0 23 Dec 2021 L1 U3 non-standard No Details →
2.8.1 29 Nov 2021 L1 U3 non-standard No Details →
2.8.0 09 Oct 2021 L1 U3 non-standard No Details →
2.7.2 30 Aug 2020 L1 U3 non-standard No Details →
2.7.1 09 Dec 2019 L1 U3 non-standard No Details →
2.7.0 03 Dec 2019 L1 U3 non-standard No Details →
2.6.0 23 Jun 2019 L1 U3 non-standard No Details →
2.5.1 23 Jun 2019 L1 U3 non-standard No Details →
2.4.3 23 Jun 2019 L1 U2 non-standard No Details →
2.5.0 10 Jun 2019 L1 U3 non-standard No Details →
2.4.2 19 Sep 2018 L1 U2 non-standard No Details →
2.3.3 19 Sep 2018 L1 U2 non-standard No Details →
2.2.4 19 Sep 2018 L1 U2 non-standard No Details →
2.1.6 19 Sep 2018 L1 U2 non-standard No Details →
2.0.9 19 Sep 2018 L1 U2 non-standard No Details →
2.4.1 13 Mar 2018 H1 L1 U2 non-standard No Details →
2.3.2 13 Mar 2018 L1 U2 non-standard No Details →
2.2.3 13 Mar 2018 L1 U2 non-standard No Details →
2.1.5 13 Mar 2018 L1 U2 non-standard No Details →
2.0.8 13 Mar 2018 L1 U3 non-standard No Details →
1.18.5 13 Mar 2018 L1 U3 non-standard No Details →
1.17.6 13 Mar 2018 L1 U3 non-standard No Details →
2.4.0 14 Nov 2017 H1 L1 U2 non-standard No Details →
2.3.1 22 Sep 2017 L1 U3 non-standard No Details →
2.3.0 18 Sep 2017 L1 U3 non-standard No Details →
2.2.2 18 Sep 2017 L1 U3 non-standard No Details →
2.1.4 18 Sep 2017 L1 U3 non-standard No Details →
2.0.7 18 Sep 2017 C1 L1 U4 non-standard No Details →
1.18.4 18 Sep 2017 L1 U4 non-standard No Details →
2.2.1 13 Jun 2017 L1 U3 non-standard No Details →
2.2.0 09 Jun 2017 L1 U3 non-standard No Details →
2.1.3 09 Jun 2017 L1 U3 non-standard No Details →
2.0.6 09 Jun 2017 C1 L1 U4 non-standard No Details →
1.18.3 09 Jun 2017 L1 U4 non-standard No Details →
1.17.5 09 Jun 2017 L1 U4 non-standard No Details →
2.1.2 21 Feb 2017 L1 U3 non-standard No Details →
2.0.5 21 Feb 2017 C1 L1 U4 non-standard No Details →
1.18.2 21 Feb 2017 L1 U4 non-standard No Details →
1.17.4 21 Feb 2017 L1 U4 non-standard No Details →
2.1.1 13 Dec 2016 L1 U3 non-standard No Details →
2.0.4 13 Dec 2016 C1 L1 U4 non-standard No Details →
1.18.1 13 Dec 2016 L1 U4 non-standard No Details →
2.1.0 09 Dec 2016 L1 U3 non-standard No Details →
1.17.3 09 Dec 2016 L1 U4 non-standard No Details →
2.0.3 09 Dec 2016 C1 L1 U4 non-standard No Details →
1.18.0 09 Dec 2016 L1 U4 non-standard No Details →
2.0.2 26 Jul 2016 C1 L1 U4 non-standard No Details →
1.17.2 26 Jul 2016 L1 U4 non-standard No Details →
1.16.3 26 Jul 2016 L1 U4 non-standard No Details →
2.0.1 21 Jun 2016 C1 L1 U4 non-standard No Details →
1.17.1 21 Jun 2016 L1 U4 non-standard No Details →
1.16.2 21 Jun 2016 L1 U4 non-standard No Details →
2.0.0 29 Apr 2016 C1 L1 U4 non-standard No Details →
1.17.0 29 Apr 2016 L1 U4 non-standard No Details →
1.16.1 29 Apr 2016 L1 U4 non-standard No Details →
1.15.5 29 Apr 2016 L1 U4 non-standard No Details →
1.16.0 05 Nov 2015 L1 U4 non-standard No Details →
1.15.4 03 Nov 2015 L1 U4 non-standard No Details →
1.14.3 03 Nov 2015 L1 U4 non-standard No Details →
1.13.4 03 Nov 2015 L1 U4 non-standard No Details →
1.15.3 02 Oct 2015 L1 U4 non-standard No Details →
1.15.2 19 Dec 2014 L1 U4 non-standard No Details →
1.14.2 19 Dec 2014 L1 U4 non-standard No Details →
1.13.3 19 Dec 2014 L1 U4 non-standard No Details →
1.15.1 22 Sep 2014 L1 U4 non-standard No Details →
1.15.0 18 Sep 2014 L1 U4 non-standard No Details →
1.14.1 26 Aug 2014 L1 U4 non-standard No Details →
1.13.2 26 Aug 2014 L1 U4 non-standard No Details →
1.14.0 07 May 2014 L1 U4 non-standard No Details →
1.13.1 07 May 2014 L1 U4 non-standard No Details →
1.12.4 07 May 2014 L1 U4 non-standard No Details →
1.11.6 07 May 2014 L1 U4 — No Details →
1.13.0 14 Mar 2014 L1 U4 — No Details →
1.12.3 14 Mar 2014 L1 U4 — No Details →
1.11.5 14 Mar 2014 L1 U4 — No Details →
1.10.7 14 Mar 2014 L1 U4 — No Details →
1.12.2 14 Feb 2014 L1 U4 — No Details →
1.11.4 14 Feb 2014 L1 U4 — No Details →
1.10.6 14 Feb 2014 L1 U4 — No Details →
1.12.1 09 Jan 2014 L1 U4 — No Details →
1.11.3 09 Jan 2014 L1 U4 — No Details →
1.10.5 09 Jan 2014 L1 U4 — No Details →
1.12.0 28 Sep 2013 L1 U4 — No Details →
1.11.2 28 Sep 2013 L1 U4 — No Details →
1.10.4 28 Sep 2013 L1 U4 — No Details →
1.11.1 21 Sep 2013 L1 U4 — No Details →
1.10.3 21 Sep 2013 L1 U4 — No Details →
1.11.0 26 Jul 2013 L1 U4 — No Details →
1.10.2 26 Jul 2013 L1 U4 — No Details →
1.10.1 05 Apr 2013 L1 U4 — No Details →
1.10.0 01 Mar 2013 L1 U4 — No Details →

The newest 120 of 153 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 1
  • 2018 4
  • 2022 3
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for paramiko

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-7750: Paramiko SSH Server Authentication Bypass 9.8 critical 2.0.8 12 Jul 2018
CVE-2018-1000805: Paramiko Authentication Bypass Vulnerability 8.8 high 2.4.2 10 Oct 2018
CVE-2008-0299: Paramiko Unsafe randomness usage may allow access to sensitive information 6.5 high 1.7.1-3 01 May 2022
CVE-2022-24302: Race Condition in Paramiko 5.9 high 2.10.1 19 Mar 2022
CVE-2023-48795: Paramiko Package Suffers from Prefix Truncation Attack Vulnerability 5.9 medium 3.4.0 07 Jul 2026

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 paramiko

Is paramiko safe to use?

Vulert records 11 vulnerabilities for paramiko in PyPI: 1 critical, 3 high, 0 medium and 1 low, plus 6 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is paramiko's Vulert package health score?

Vulert scores paramiko 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of paramiko affected?

Yes. 5.1.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of paramiko should I use?

5.1.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 paramiko have?

11 vulnerabilities are recorded for paramiko in the PyPI ecosystem: 1 critical, 3 high, 0 medium and 1 low, plus 6 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new paramiko vulnerabilities disclosed?

3 vulnerabilities were recorded for paramiko in the last 12 months, and the oldest entry in this database dates to 16 Jan 2008. 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 paramiko 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 paramiko for upcoming vulnerabilities?

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