OpenSSH vulnerabilitiesRanked by how likely they are to be used.
OpenSSH is made by OpenBSD. We track 118 published vulnerabilities in it, across 128 versions. None of them is on the list of flaws known to be exploited today. If you run OpenSSH, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which OpenSSH vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of OpenSSH's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which OpenSSH flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2024-6387High
A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd).
- 94%CVE-2023-48795Medium
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension...
- 90%CVE-2023-25136Medium
OpenSSH server (sshd) 9.1 introduced a double-free vulnerability during options.kex_algorithms handling.
- 89%CVE-2016-6210Medium
sshd in OpenSSH before 7.3, when SHA256 or SHA512 are used for user password hashing, uses BLOWFISH hashing on a static password when the username does not exist, which allows remote attackers to enumerate users by...
- 80%CVE-2023-38408Critical
The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system.
- 77%CVE-2003-0190Medium
OpenSSH-portable (OpenSSH) 3.6.1p1 and earlier with PAM support enabled immediately sends an error message when a user does not exist, which allows remote attackers to determine valid usernames via a timing attack.
- 63%CVE-2016-0777Medium
The resend_bytes function in roaming_common.c in the client in OpenSSH 5.x, 6.x, and 7.x before 7.1p2 allows remote servers to obtain sensitive information from process memory by requesting transmission of an entire...
- 59%CVE-2016-6515High
The auth_password function in auth-passwd.c in sshd in OpenSSH before 7.3 does not limit password lengths for password authentication, which allows remote attackers to cause a denial of service (crypt CPU...
- 58%
OpenSSH portable 4.1 on SUSE Linux, and possibly other platforms and versions, and possibly under limited configurations, allows remote attackers to determine valid usernames via timing discrepancies in which...
Running OpenSSH? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.
- Matched to
- OpenSSH on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 118 published vulnerabilities listed under the name OpenSSH, across 128 versions.
None of OpenSSH's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track OpenSSH. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.