SSH vulnerabilities

By year

Bars are flaws published each year; the red part is the share attackers have used.

Latest high and critical flaws

• CVE-2025-32942 SSH Tectia Server before 6.6.6 sometimes allows attackers to read and alter a user's session traffic.High 7.2 · Oct 2, 2025
• CVE-2021-27893 SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation in nonstandard conditions.High 7 · Mar 15, 2021
• CVE-2021-27892 SSH Tectia Client and Server before 6.4.19 on Windows allow local privilege escalation.High 7.8 · Mar 15, 2021
• CVE-2021-27891 SSH Tectia Client and Server before 6.4.19 on Windows have weak key generation.High 8.8 · Mar 15, 2021
• CVE-2012-5975 The SSH USERAUTH CHANGE REQUEST feature in SSH Tectia Server 6.0.4 through 6.0.20, 6.1.0 through 6.1.12, 6.2.0 through 6.2.5, and 6.3.0 through 6.3.2 on UNIX anHigh 9.3 · Dec 4, 2012
• CVE-2007-5616 ssh-signer in SSH Tectia Client and Server 5.x before 5.2.4, and 5.3.x before 5.3.6, on Unix and Linux allows local users to gain privileges via unspecified vecHigh 7.2 · Jan 9, 2008
• CVE-2006-4315 Unquoted Windows search path vulnerability in multiple SSH Tectia products, including Client/Server/Connector 5.0.0 and 5.0.1 and Client/Server before 4.4.5, anHigh 7.2 · Aug 23, 2006
• CVE-2006-4316 SSH Tectia Management Agent 2.1.2 allows local users to gain root privileges by running a program called sshd, which is obtained from a process listing when theHigh 7.2 · Aug 23, 2006
• CVE-2005-4310 SSH Tectia Server 5.0.0 (A, F, and T), when allowing host-based authentication only, allows users to log in with the wrong credentials.High 7.5 · Dec 16, 2005
• CVE-2002-1646 SSH Secure Shell for Servers 3.0.0 to 3.1.1 allows remote attackers to override the AllowedAuthentications configuration and use less secure authentication scheHigh 7.5 · Dec 31, 2002
• CVE-2002-1715 SSH 1 through 3, and possibly other versions, allows local users to bypass restricted shells such as rbash or rksh by uploading a script to a world-writeable diHigh 7.2 · Dec 31, 2002
• CVE-2002-1644 SSH Secure Shell for Servers and SSH Secure Shell for Workstations 2.0.13 through 3.2.1, when running without a PTY, does not call setsid to remove the child prHigh 7.2 · Nov 25, 2002
• CVE-2002-1645 Buffer overflow in the URL catcher feature for SSH Secure Shell for Workstations client 3.1 to 3.2.0 allows remote attackers to execute arbitrary code via a lonHigh 10 · Nov 25, 2002
• CVE-2001-0553 SSH Secure Shell 3.0.0 on Unix systems does not properly perform password authentication to the sshd2 daemon, which allows local users to gain access to accountHigh 7.2 · Aug 14, 2001
• CVE-2001-0471 SSH daemon version 1 (aka SSHD-1 or SSH-1) 1.2.30 and earlier does not log repeated login attempts, which could allow remote attackers to compromise accounts wiHigh 7.5 · Jun 27, 2001
• CVE-2001-1473 The SSH-1 protocol allows remote servers to conduct man-in-the-middle attacks and replay a client challenge response to a target server by creating a Session IDHigh 7.5 · Jan 18, 2001
• CVE-2001-1475 SSH before 2.0, when using RC4 and password authentication, allows remote attackers to replay messages until a new server key (VK) is generated.High 7.5 · Jan 18, 2001
• CVE-2001-1476 SSH before 2.0, with RC4 encryption and the "disallow NULL passwords" option enabled, makes it easier for remote attackers to guess portions of user passwords bHigh 7.5 · Jan 18, 2001
• CVE-2000-0575 SSH 1.2.27 with Kerberos authentication support stores Kerberos tickets in a file which is created in the current directory of the user who is logging in, whichHigh 7.2 · Jul 5, 2000
• CVE-1999-1029 SSH server (sshd2) before 2.0.12 does not properly record login attempts if the connection is closed before the maximum number of tries, allowing a remote attacHigh 7.5 · May 13, 1999
• CVE-1999-0248 A race condition in the authentication agent mechanism of sshd 1.2.17 allows an attacker to steal another user's credentials.High 10 · Jan 1, 1999