OpenSSH vulnerabilities: known CVEs & security history
OpenBSD · Remote access · 123 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all OpenSSH release lines — 123 in total. A CVE here doesn't mean your version is affected — check OpenSSH's current status and the safe version to run.
Known OpenSSH CVEs
Actively-exploited and most-severe first. Showing the top 80 of 123. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2023-38408 | critical | 9.8 | 77% | 2023 |
| CVE-2023-28531 | critical | 9.8 | 2% | 2023 |
| CVE-2016-1908 | critical | 9.8 | 14% | 2017 |
| CVE-2010-4478 | critical | 9.8 | 4% | 2010 |
| CVE-2002-0639 | critical | 9.8 | 18% | 2002 |
| CVE-2002-0083 | critical | 9.8 | 15% | 2002 |
| CVE-2003-0786 | high | 10 | 3% | 2003 |
| CVE-2003-0693 | high | 10 | 10% | 2003 |
| CVE-2002-0640 | high | 10 | 27% | 2002 |
| CVE-2001-0144 | high | 10 | 32% | 2001 |
| CVE-2000-0999 | high | 10 | 12% | 2000 |
| CVE-2000-0525 | high | 10 | 3% | 2000 |
| CVE-2008-3844 | high | 9.3 | 3% | 2008 |
| CVE-2024-6387 | high | 8.1 | 100% | 2024 |
| CVE-2016-0778 | high | 8.1 | 20% | 2016 |
| CVE-2015-5600 | high | 8.1 | 9% | 2015 |
| CVE-2006-5051 | high | 8.1 | 44% | 2006 |
| CVE-2019-16905 | high | 7.8 | 2% | 2019 |
| CVE-2016-10012 | high | 7.8 | 1% | 2017 |
| CVE-2015-8325 | high | 7.8 | 1% | 2016 |
| CVE-2006-4924 | high | 7.8 | 34% | 2006 |
| CVE-2003-1562 | high | 7.6 | 6% | 2003 |
| CVE-2026-35385 | high | 7.5 | 0% | 2026 |
| CVE-2026-3497 | high | 7.5 | 2% | 2026 |
| CVE-2020-12062 | high | 7.5 | 2% | 2020 |
| CVE-2016-10708 | high | 7.5 | 16% | 2018 |
| CVE-2016-8858 | high | 7.5 | 29% | 2016 |
| CVE-2016-6515 | high | 7.5 | 58% | 2016 |
| CVE-2010-5107 | high | 7.5 | 17% | 2013 |
| CVE-2011-0539 | high | 7.5 | 2% | 2011 |
| CVE-2007-4752 | high | 7.5 | 2% | 2007 |
| CVE-2006-5794 | high | 7.5 | 3% | 2006 |
| CVE-2003-0787 | high | 7.5 | 2% | 2003 |
| CVE-2003-0682 | high | 7.5 | 9% | 2003 |
| CVE-2003-0695 | high | 7.5 | 4% | 2003 |
| CVE-2003-0386 | high | 7.5 | 6% | 2003 |
| CVE-2002-0765 | high | 7.5 | 1% | 2002 |
| CVE-2002-0575 | high | 7.5 | 4% | 2002 |
| CVE-2001-1507 | high | 7.5 | 2% | 2001 |
| CVE-2001-0816 | high | 7.5 | 2% | 2001 |
| CVE-2001-1380 | high | 7.5 | 3% | 2001 |
| CVE-2001-0572 | high | 7.5 | 7% | 2001 |
| CVE-2001-1459 | high | 7.5 | 2% | 2001 |
| CVE-2000-1169 | high | 7.5 | 2% | 2001 |
| CVE-2020-15778 | high | 7.4 | 13% | 2020 |
| CVE-2016-10009 | high | 7.3 | 37% | 2017 |
| CVE-2014-1692 | high | 7.3 | 5% | 2014 |
| CVE-2015-6565 | high | 7.2 | 3% | 2015 |
| CVE-2001-0872 | high | 7.2 | 1% | 2001 |
| CVE-2001-0529 | high | 7.2 | 1% | 2001 |
| CVE-2021-28041 | high | 7.1 | 3% | 2021 |
| CVE-2023-51767 | high | 7 | 1% | 2023 |
| CVE-2021-41617 | high | 7 | 2% | 2021 |
| CVE-2016-10010 | high | 7 | 4% | 2017 |
| CVE-2015-6564 | high | 7 | 1% | 2015 |
| CVE-2009-2904 | medium | 6.9 | 0% | 2009 |
| CVE-2008-1483 | medium | 6.9 | 0% | 2008 |
| CVE-2025-26465 | medium | 6.8 | 7% | 2025 |
| CVE-2019-6110 | medium | 6.8 | 21% | 2019 |
| CVE-2019-6109 | medium | 6.8 | 4% | 2019 |
| CVE-2004-2760 | medium | 6.8 | 9% | 2004 |
| CVE-2001-1585 | medium | 6.8 | 2% | 2001 |
| CVE-2023-51385 | medium | 6.5 | 20% | 2023 |
| CVE-2023-25136 | medium | 6.5 | 90% | 2023 |
| CVE-2016-0777 | medium | 6.5 | 63% | 2016 |
| CVE-2014-2653 | medium | 6.5 | 2% | 2014 |
| CVE-2012-0814 | medium | 6.5 | 4% | 2012 |
| CVE-2008-3234 | medium | 6.5 | 6% | 2008 |
| CVE-2008-1657 | medium | 6.5 | 2% | 2008 |
| CVE-2016-3115 | medium | 6.4 | 37% | 2016 |
| CVE-2015-6563 | medium | 6.4 | 0% | 2015 |
| CVE-2004-1653 | medium | 6.4 | 12% | 2004 |
| CVE-2016-10011 | medium | 6.2 | 1% | 2017 |
| CVE-2013-4548 | medium | 6 | 3% | 2013 |
| CVE-2025-26466 | medium | 5.9 | 38% | 2025 |
| CVE-2023-48795 | medium | 5.9 | 93% | 2023 |
| CVE-2020-14145 | medium | 5.9 | 2% | 2020 |
| CVE-2019-6111 | medium | 5.9 | 58% | 2019 |
| CVE-2016-6210 | medium | 5.9 | 89% | 2017 |
| CVE-2023-51384 | medium | 5.5 | 0% | 2023 |
43 older / lower-severity CVEs not shown — see OpenSSH's full record.
Is my OpenSSH version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your OpenSSH version → · Monitor OpenSSH for new CVEs →
OpenSSH vulnerabilities — frequently asked
How many known vulnerabilities does OpenSSH have?
IsItPatched tracks 123 CVEs for OpenSSH. 6 are critical-severity and 49 high-severity. These span every release line — what matters is whether the version you run is affected.
Does OpenSSH have any actively-exploited vulnerabilities?
None of OpenSSH's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe OpenSSH vulnerability?
Among tracked issues, CVE-2023-38408 (CRITICAL, CVSS 9.8) ranks highest — a CWE-428 weakness.
Is OpenSSH safe to use?
It depends on the version. The latest supported OpenSSH release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: OpenSSH security status · OpenSSH end-of-life · actively-exploited CVEs. Always verify against OpenBSD's advisories — see our disclaimer.