PatchTheCVElibssh vulnerabilities
Recent CVEs affecting libssh products. 11 tracked.
libssh has 11 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-07-21. Highest priority: CVE-2026-59851 (score 46/100).
- CVE-2026-59849 LOW 3.1 UPGRADE MITIGATE A flaw was found in libssh
- CVE-2026-59842 LOW 3.7 DOWNGRADE MITIGATE A flaw was found in libssh
- CVE-2026-15370 MEDIUM 6.7 UPGRADE MITIGATE A flaw was found in libssh
- CVE-2026-59847 MEDIUM 5.9 UPGRADE MITIGATE A flaw was found in libssh
- CVE-2026-59850 MEDIUM 4.3 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59848 MEDIUM 5.3 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59846 LOW 3.9 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59845 MEDIUM 5.3 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59844 MEDIUM 6.5 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59843 MEDIUM 6.5 MITIGATE MITIGATE A flaw was found in libssh
- CVE-2026-59851 HIGH 8.8 MITIGATE MITIGATE A flaw was found in libssh
FAQ
How do I fix libssh vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libssh being exploited right now?
None of the tracked libssh CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libssh CVE should I patch first?
CVE-2026-59851 currently ranks highest (46/100): A flaw was found in libssh.