Vulnerability Database · PyPI · asyncssh · Version

asyncssh 2.0.0

2.0.0 is affected by 11 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.24.1.

Critical 0 High 3 Medium 8 Low 0 Unrated 0

Released 26 Oct 2019 Licence non-standard Also known from other sources 11 Newer releases 93 Database updated 22/Oct/2026

Release and licence data published by PyPI. 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.

Looking for another version, or everything Vulert holds for asyncssh?

All versions → Full vulnerability list →

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 2.0.0

Is asyncssh 2.0.0 vulnerable?

Yes. 11 vulnerabilities in the Vulert database cover asyncssh 2.0.0: 0 critical, 3 high, 8 medium and 0 low. The upgrade Vulert recommends is 2.24.1, and each entry above names the fixed version to move to.

Which version of asyncssh should I use instead of 2.0.0?

2.24.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 2.0.0 the latest release of asyncssh?

No. 2.0.0 was published 26 Oct 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.