VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libssh2: vulnerability history, versions and safety

libssh2 is a package in the OSS-Fuzz ecosystem. Vulert records 9 vulnerabilities for it across 2 releases, from Jan 2022 to Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H2 M2 U5
i
3 with no fix published

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

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

Nothing new recorded in the last year.

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: 3 of the 9 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 9 vulnerabilities on record across 3 years, none in the last year.

What to do: Plan around the 3 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 9 over 3 years · 0 in the last year i
  • Latest disclosure 05 Jun 2025 i
  • Highest CVSS n/a i
  • With no published fix 3 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.

i
Version Vulert vulnerabilities Fix published Details
libssh2-1.11.1 U5 No Details →
libssh2-1.11.0 M1 U3 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2024 3
  • 2025 3

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

03 Vulnerabilities

Recorded vulnerabilities for libssh2

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Null-dereference READ in session_startup in libssh2 N/A unrated b89858b83d68d7e29e0c5b0bb803f8a68271710c 09 Jan 2022
Heap-buffer-overflow in libssh2: _libssh2_ntohu32 N/A medium 88a960a86b9ffbabd17a4bbcf767e26514c4678e 25 Apr 2023
Heap-buffer-overflow in libssh2: _libssh2_kex_agree_instr N/A medium f52ffc1ccdedcd5a885e85c2d0f0cb872b2b0a7f 22 Dec 2023
Null-dereference READ in libssh2_packet_add N/A unrated b89858b83d68d7e29e0c5b0bb803f8a68271710c 16 Aug 2024
Heap-double-free vulnerability in libssh2_default_free N/A high b3465418471ffa4cf0bbe1e8f28c4d007f060f99 16 Aug 2024

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 9 vulnerabilities for libssh2 in OSS-Fuzz: 0 critical, 2 high, 2 medium and 0 low, plus 5 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libssh2 have?

9 vulnerabilities are recorded for libssh2 in the OSS-Fuzz ecosystem: 0 critical, 2 high, 2 medium and 0 low, plus 5 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?

0 vulnerabilities were recorded for libssh2 in the last 12 months, and the oldest entry in this database dates to 09 Jan 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 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.