VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libssh2: vulnerability history, versions and safety

libssh2 is a package in the Debian ecosystem. Vulert records 26 vulnerabilities for it across 19 releases, from Mar 2015 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
26 vulnerabilities recorded U26
i
10 with no fix published

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

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

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libssh2 vulnerabilities

Vulert verdict on libssh2 i

Updated on 23 Oct 2026

Careful: 10 of the 26 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 26 vulnerabilities on record across 11 years, 10 in the last year.

What to do: Plan around the 10 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 26 over 11 years · 10 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 10 i

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 holds for libssh2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 19 of 19 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2015 2
  • 2016 1
  • 2019 11
  • 2023 2
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for libssh2

The 5 most severe of 26 vulnerabilities recorded for this package

Search all 26 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Out of Bounds Memory Access in libssh2 - CVE-2020-22218 7.5 high 1.9.0-2+deb11u1 22 Aug 2023
Integer Overflow Vulnerability in libssh2: CVE-2026-7598 7.3 high No fix published 01 May 2026
Heap Buffer Overflow in libssh2 Due to Attribute Count Mismanagement 7.0 high No fix published 28 Jun 2026
Out-of-Bounds Heap Read Vulnerability in libssh2: CVE-2025-15661 6.5 medium No fix published 18 Jun 2026
Critical Vulnerability in libssh2: Uninitialized Memory Exposure 6.5 medium No fix published 28 Jun 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 libssh2

Is libssh2 safe to use?

Vulert records 26 vulnerabilities for libssh2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 26 not yet rated. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libssh2 have?

26 vulnerabilities are recorded for libssh2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 26 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 libssh2 vulnerabilities disclosed?

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

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