Libssh
18 known vulnerabilities
Top Products
A flaw was found in libssh. On servers with GSSAPIKeyExchange enabled, the gssapi-keyex path does not verify whether the
A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invok
A flaw was found in libssh. Logic errors in automatic certificate-based public key authentication can cause libssh clien
A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep
A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively re
A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metachara
A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; durin
A flaw was found in libssh. A remote authenticated client can issue SSH_FXP_READ requests with an arbitrarily large leng
A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN
A flaw was found in libssh. During server-side GSSAPI key exchange, a client-supplied Curve25519 public key shorter than
A flaw was found in libssh. During SFTP server directory listing, the longname field is constructed with unsafe concaten
A flaw was found in libssh. This vulnerability allows local man-in-the-middle attacks, security downgrades of SSH (Secur
A flaw was found in libssh in which a malicious SFTP (SSH File Transfer Protocol) server can exploit this by sending a m
A flaw was found in libssh. A remote attacker, by controlling client configuration files or known_hosts files, could cra
A flaw was found in libssh. The API function `ssh_get_hexa()` is vulnerable to a denial of service when processing zero-
A flaw was found in libssh where it can attempt to open arbitrary files during configuration parsing. A local attacker c
A malicious SCP server can send unexpected paths that could make the client application override local files outside of
A weakness has been identified in libssh up to 0.11.3. The impacted element is the function sftp_extensions_get_name/sft
Frequently Asked Questions
How many CVEs affect Libssh?
Libssh has 18 CVE records in our database, including 0 critical and 3 high severity vulnerabilities.
What are the most severe Libssh vulnerabilities?
Libssh has 0 critical severity (CVSS 9.0+) and 3 high severity (CVSS 7.0-8.9) vulnerabilities. Review the list above sorted by publication date to find the most recent high-severity issues.
How can I scan for Libssh vulnerabilities?
CyberStrike's AI-powered security agents automatically detect vulnerabilities in Libssh products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.
Detect Libssh Vulnerabilities
CyberStrike scans your infrastructure for Libssh vulnerabilities and provides real-time remediation guidance.
Get Started