VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

asyncssh: vulnerability history, versions and safety

asyncssh is a package in the PyPI ecosystem. Vulert records 15 vulnerabilities for it across 118 releases, from Mar 2018 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded C1 H2 M5 U7
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all asyncssh vulnerabilities

Vulert verdict on asyncssh 2.24.1 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.24.1 — unaffected i
  • Vulnerabilities on record 15 over 8 years · 8 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 701 packages i
  • Stars 1,761 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence EPL-2.0 OR GPL-2.0-or-later 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 asyncssh, 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
2.24.1 04 Oct 2026 none EPL-2.0 OR GPL-2.0-or-later — Details →
2.24.0 27 Jun 2026 none EPL-2.0 OR GPL-2.0-or-later — Details →
2.23.1 07 Jun 2026 M1 U1 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.23.0 09 May 2026 H1 M2 U3 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.22.0 21 Dec 2025 H1 M3 U4 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.21.1 28 Sep 2025 H1 M2 U3 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.21.0 03 May 2025 H1 M2 U3 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.20.0 17 Feb 2025 H1 M2 U3 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.19.0 13 Dec 2024 H1 M2 U3 EPL-2.0 OR GPL-2.0-or-later Yes Details →
2.18.0 26 Oct 2024 H1 M2 U3 non-standard Yes Details →
2.17.0 02 Sep 2024 H1 M2 U3 non-standard Yes Details →
2.16.0 18 Aug 2024 H1 M2 U3 non-standard Yes Details →
2.15.0 03 Jul 2024 H1 M2 U3 non-standard Yes Details →
2.14.2 18 Dec 2023 H1 M2 U3 non-standard Yes Details →
2.14.1 09 Nov 2023 H1 M3 U3 non-standard Yes Details →
2.14.0 01 Oct 2023 H2 M4 U5 non-standard Yes Details →
2.13.2 22 Jun 2023 H2 M4 U5 non-standard Yes Details →
2.13.1 18 Feb 2023 H2 M4 U5 non-standard Yes Details →
2.13.0 27 Dec 2022 H2 M4 U5 non-standard Yes Details →
2.12.0 11 Aug 2022 H2 M4 U5 non-standard Yes Details →
2.11.0 04 Jun 2022 H2 M4 U5 non-standard Yes Details →
2.10.1 16 Apr 2022 H2 M4 U5 non-standard Yes Details →
2.10.0 26 Mar 2022 H2 M4 U5 non-standard Yes Details →
2.9.0 23 Jan 2022 H2 M4 U5 non-standard Yes Details →
2.8.1 08 Nov 2021 H2 M4 U5 non-standard Yes Details →
2.8.0 04 Nov 2021 H2 M4 U5 non-standard Yes Details →
2.7.2 16 Sep 2021 H2 M4 U5 non-standard Yes Details →
2.7.1 06 Sep 2021 H2 M4 U5 non-standard Yes Details →
2.7.0 19 Jun 2021 H2 M4 U5 non-standard Yes Details →
2.6.0 01 May 2021 H2 M4 U5 non-standard Yes Details →
2.5.0 23 Dec 2020 H2 M4 U5 non-standard Yes Details →
2.4.2 12 Sep 2020 H2 M4 U5 non-standard Yes Details →
2.4.1 05 Sep 2020 H2 M4 U5 non-standard Yes Details →
2.4.0 29 Aug 2020 H2 M4 U5 non-standard Yes Details →
2.3.0 12 Jul 2020 H2 M4 U5 non-standard Yes Details →
2.2.1 18 Apr 2020 H2 M4 U5 non-standard Yes Details →
2.2.0 29 Feb 2020 H2 M4 U5 non-standard Yes Details →
2.1.0 30 Nov 2019 H2 M4 U5 non-standard Yes Details →
2.0.1 02 Nov 2019 H2 M4 U5 non-standard Yes Details →
2.0.0 26 Oct 2019 H2 M4 U5 non-standard Yes Details →
1.18.0 24 Aug 2019 H2 M4 U5 non-standard Yes Details →
1.17.1 24 Jul 2019 H2 M4 U5 non-standard Yes Details →
1.17.0 01 Jun 2019 H2 M4 U5 non-standard Yes Details →
1.16.1 31 Mar 2019 H2 M4 U5 non-standard Yes Details →
1.16.0 03 Mar 2019 H2 M4 U5 non-standard Yes Details →
1.15.1 21 Jan 2019 H2 M4 U5 non-standard Yes Details →
1.15.0 27 Nov 2018 H2 M4 U5 non-standard Yes Details →
1.14.0 08 Sep 2018 H2 M4 U5 non-standard Yes Details →
1.13.3 24 Jul 2018 H2 M4 U5 non-standard Yes Details →
1.13.2 04 Jul 2018 H2 M4 U5 non-standard Yes Details →
1.13.1 17 Jun 2018 H2 M4 U5 non-standard Yes Details →
1.13.0 20 May 2018 H2 M4 U5 non-standard Yes Details →
1.12.2 18 Apr 2018 H2 M4 U5 non-standard Yes Details →
1.12.1 10 Mar 2018 H2 M4 U5 non-standard Yes Details →
1.12.0 07 Feb 2018 C1 H2 M4 U6 non-standard Yes Details →
1.11.1 16 Nov 2017 C1 H2 M4 U6 non-standard Yes Details →
1.11.0 09 Sep 2017 C1 H2 M4 U6 non-standard Yes Details →
1.10.1 20 May 2017 C1 H2 M4 U6 non-standard Yes Details →
1.10.0 06 May 2017 C1 H2 M4 U6 non-standard Yes Details →
1.9.0 19 Feb 2017 C1 H2 M4 U6 non-standard Yes Details →
1.8.1 30 Dec 2016 C1 H2 M4 U6 non-standard Yes Details →
1.8.0 29 Dec 2016 C1 H2 M4 U6 non-standard Yes Details →
1.7.3 23 Nov 2016 C1 H2 M4 U6 non-standard Yes Details →
1.7.2 29 Oct 2016 C1 H2 M4 U6 non-standard Yes Details →
1.7.1 08 Oct 2016 C1 H2 M4 U6 non-standard Yes Details →
1.6.2 04 Sep 2016 C1 H2 M4 U6 non-standard Yes Details →
1.6.1 28 Aug 2016 C1 H2 M4 U6 non-standard Yes Details →
1.6.0 13 Aug 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.6 18 Jun 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.5 11 Jun 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.4 07 Jun 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.3 03 Apr 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.2 26 Feb 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.1 24 Feb 2016 C1 H2 M4 U6 non-standard Yes Details →
1.5.0 28 Jan 2016 C1 H2 M4 U6 non-standard Yes Details →
1.4.1 24 Jan 2016 C1 H2 M4 U6 non-standard Yes Details →
1.4.0 18 Jan 2016 C1 H2 M4 U6 non-standard Yes Details →
1.3.2 27 Nov 2015 C1 H2 M4 U6 non-standard Yes Details →
1.3.1 06 Nov 2015 C1 H2 M4 U6 non-standard Yes Details →
1.3.0 10 Oct 2015 C1 H2 M4 U6 non-standard Yes Details →
1.2.1 27 Aug 2015 C1 H2 M4 U6 non-standard Yes Details →
1.2.0 06 Jun 2015 C1 H2 M4 U6 non-standard Yes Details →
1.1.1 25 May 2015 C1 H2 M4 U6 non-standard Yes Details →
1.1.0 23 May 2015 C1 H2 M4 U6 non-standard Yes Details →
1.0.1 14 Apr 2015 C1 H2 M4 U6 non-standard Yes Details →
1.0.0 11 Apr 2015 C1 H2 M4 U6 non-standard Yes Details →
0.9.2 27 Jan 2015 C1 H2 M4 U6 non-standard Yes Details →
0.9.1 05 Dec 2014 C1 H2 M4 U6 non-standard Yes Details →
0.9.0 15 Nov 2014 C1 H2 M4 U6 non-standard Yes Details →
0.8.4 13 Sep 2014 C1 H2 M4 U6 non-standard Yes Details →
0.8.3 16 Aug 2014 C1 H2 M4 U6 non-standard Yes Details →
0.8.2 16 Aug 2014 C1 H2 M4 U6 non-standard Yes Details →
0.8.1 16 Aug 2014 C1 H2 M4 U6 non-standard Yes Details →
0.8.4-py3.4 — C1 H2 M4 U5 — Yes Details →
0.9.0-py3.4 — C1 H2 M4 U5 — Yes Details →
0.9.1-py3.4 — C1 H2 M4 U5 — Yes Details →
0.9.2-py3.4 — C1 H2 M4 U5 — Yes Details →
1.0.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.0.1-py3.4 — C1 H2 M4 U5 — Yes Details →
1.1.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.1.1-py3.4 — C1 H2 M4 U5 — Yes Details →
1.10.0-py3.5 — C1 H2 M4 U5 — Yes Details →
1.10.1-py3.5 — C1 H2 M4 U5 — Yes Details →
1.11.0-py3.5 — C1 H2 M4 U5 — Yes Details →
1.11.1-py3.5 — C1 H2 M4 U5 — Yes Details →
1.12.0-py3.5 — C1 H2 M4 U5 — Yes Details →
1.12.1-py3.5 — H2 M4 U5 — Yes Details →
1.12.2-py3.5 — H2 M4 U5 — Yes Details →
1.13.0-py3.5 — H2 M4 U5 — Yes Details →
1.13.1-py3.5 — H2 M4 U5 — Yes Details →
1.13.2-py3.5 — H2 M4 U5 — Yes Details →
1.2.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.2.1-py3.4 — C1 H2 M4 U5 — Yes Details →
1.3.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.3.1-py3.4 — C1 H2 M4 U5 — Yes Details →
1.3.2-py3.4 — C1 H2 M4 U5 — Yes Details →
1.4.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.4.1-py3.4 — C1 H2 M4 U5 — Yes Details →
1.5.0-py3.4 — C1 H2 M4 U5 — Yes Details →
1.5.1-py3.4 — C1 H2 M4 U5 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 1
  • 2023 5
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for asyncssh

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2018-7749: AsyncSSH SSH Server Authentication Bypass 9.8 critical 1.12.1 14 May 2022
CVE-2026-54591: asyncssh Arbitrary File Write Vulnerability via SCP Path Traversal 8.1 high 2.23.1 10 Sep 2026
CVE-2026-54591: asyncssh SCP Path Traversal Vulnerability Leading to Arbitrary File Write 8.1 high 2.23.1 26 Aug 2026
CVE-2023-46446: AsyncSSH Rogue Session Attack 8.1 high 2.14.1 09 Nov 2023
CVE-2026-45309: AsyncSSH Path Traversal Vulnerability Allows Unauthorized SSH Authentication 6.9 medium 2.23.0 27 May 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 asyncssh

Is asyncssh safe to use?

Vulert records 15 vulnerabilities for asyncssh in PyPI: 1 critical, 2 high, 5 medium and 0 low, plus 7 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is asyncssh's Vulert package health score?

Vulert scores asyncssh 62/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).

Is the latest version of asyncssh affected?

No. 2.24.1, 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 asyncssh should I use?

2.24.1 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 asyncssh have?

15 vulnerabilities are recorded for asyncssh in the PyPI ecosystem: 1 critical, 2 high, 5 medium and 0 low, plus 7 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 asyncssh vulnerabilities disclosed?

8 vulnerabilities were recorded for asyncssh in the last 12 months, and the oldest entry in this database dates to 12 Mar 2018. 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 asyncssh 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 asyncssh for upcoming vulnerabilities?

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