Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

libssh

About This Vendor

libssh is a technology vendor producing software and infrastructure products. As a software provider, libssh's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of libssh's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 28 known vulnerabilities from libssh. This includes 1 critical-severity issue and 7 high-severity issues that represent significant risk. These vulnerabilities affect 78 distinct products across libssh's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2012 through 2026, indicating decades of continuous security attention and research. Organizations deploying libssh products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2012-4559 2012-11-30 2025-04-11 - 6.8 Likely
CVE-2012-4560 2012-11-30 2025-04-11 - 7.5 Likely
CVE-2012-4561 2012-11-30 2025-04-11 - 5.0 Likely
CVE-2012-4562 2012-11-30 2025-04-11 - 7.5 Likely
CVE-2012-6063 2012-11-30 2025-04-11 - 7.5 Likely
CVE-2013-0176 2013-02-05 2025-04-11 - 4.3 Likely
CVE-2014-0017 2014-03-14 2025-04-12 - 1.9 Unknown
CVE-2014-8132 2014-12-29 2025-04-12 - 5.0 Likely
CVE-2015-3146 2016-04-13 2025-04-12 7.5 5.0 Likely
CVE-2016-0739 2016-04-13 2025-04-12 5.9 4.3 Likely
CVE-2018-10933 2018-10-17 2024-11-21 9.1 6.4 Likely
CVE-2019-14889 2019-12-10 2024-11-21 8.8 9.3 Likely
CVE-2020-1730 2020-04-13 2024-11-21 5.3 5.0 Likely
CVE-2020-16135 2020-07-29 2024-11-21 5.9 4.3 Likely
CVE-2021-3634 2021-08-31 2024-11-21 6.5 4.0 Likely
CVE-2023-1667 2023-05-26 2024-11-21 6.5 - -
CVE-2023-2283 2023-05-26 2025-11-03 6.5 - -
CVE-2023-3603 2023-07-21 2024-11-21 3.1 - -
CVE-2023-48795 2023-12-18 2025-11-04 5.9 - -
CVE-2023-6918 2023-12-19 2025-02-15 3.7 - -
CVE-2023-6004 2024-01-03 2025-11-04 4.8 - -
CVE-2025-5318 2025-06-24 2026-02-27 8.1 - -
CVE-2025-5372 2025-07-04 2025-12-10 5.0 - -
CVE-2025-5351 2025-07-04 2026-01-08 6.5 - -
CVE-2025-5987 2025-07-07 2026-03-05 8.1 - -
CVE-2025-8114 2025-07-24 2025-11-17 4.7 - -
CVE-2025-5449 2025-07-25 2026-01-08 6.5 - -
CVE-2026-3731 2026-03-08 2026-03-12 5.3 5.0 Likely

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for libssh by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with libssh's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.