CVE

CVSS v3 Scores

Impacted OpenSSH versions

Fixed

Open

SSH

version

Description

Impact to Junos OS or Junos OS Evolved

Solution/Workaround

CVE-

2016-

20012

5.3

<= 8.7

8.8

OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product.

Not Impacted

As per the CVE Details https://nvd.nist.gov/vuln/detail/CVE-2016-20012:

“The vendor (OpenSSH) does not recognize user enumeration as a vulnerability for this product.”

CVE-2017-15906

5.3

< 7.6

7.6

The process_open function in sftp-server.c in OpenSSH before 7.6 does not properly prevent write operations in readonly mode, which allows attackers to create zero-length files.

Not Impacted

In Junos OS/Junos OS Evolved the sftp-server read-only mode is not supported at all.

Therefore, Junos OS/Junos OS Evolved is not impacted and there is no specific workaround needed.

CVE-2018-15919

5.3

5.9 - 7.8

7.9

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use.

NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

Not Impacted

Junos OS/ Junos OS Evolved does not support configuring the respective sshd option "GSSAPIAuthentication" via CLI and by default the value for the above mentioned option is set to "no".
        

CVE-2018-15473

5.3

<= 7.7

7.8

OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2hostbased.c, and auth2-pubkey.c.

Not Impacted

The affected/vulnerable components and the corresponding code are not compiled into Junos OS/Junos OS Evolved SSH.

As a result, the vulnerability is not applicable to customer systems.

CVE-2018-20685

5.3

<=7.9

8.0

In OpenSSH 7.9, scp.c in the scp client allows remote SSH servers to bypass intended access restrictions via the filename of “.” or an empty filename. The impact is modifying the permissions of the target directory on the client side. 

Not Impacted via Workaround

Customers are recommended to follow the same workaround as mentioned for CVE-2019-6109.

CVE-2019-6109

6.8

<= 7.9

 8.0

An issue was discovered in OpenSSH 7.9. Due to missing character encoding in the progress display, a malicious server (or Man-in-TheMiddle attacker) can employ crafted object names to manipulate the client output, e.g., by using ANSI control codes to hide additional files being transferred. This affects refresh_progress_meter() in progressmeter.c.

Not Impacted via Workaround

The upstream recommendation from OpenSSH developers is not to use SCP with untrusted servers due to these vulnerabilities.

Furthermore, starting from OpenSSH v9.0 SCP uses SFTP protocol by default instead of the legacy RCP/SCP protocol. SCP protocol can only be called using option “-O”.

As a workaround, customers are recommended to use SFTP (SSH File Transfer Protocol). SFTP is designed with better security mechanisms and is recommended by OpenSSH developers as a safer alternative. 

CVE-2019-6110

6.8

<= 7.9

8.0

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-TheMiddle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

Not Impacted via Workaround

Customers are recommended to follow the same workaround as mentioned for CVE-2019-6109.

CVE-2019-6111

5.9

<= 7.9

8.0

An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).

Not Impacted via Workaround

Customers are recommended to follow the same workaround as mentioned for CVE-2019-6109.

CVE-2020-15778

7.8

< 8.3

8.3

The scp in OpenSSH through 8.3p1 allows command injection in the scp.c “toremote” function, as demonstrated by backtick characters in the destination argument.

NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Not Impacted via Workaround

This scp behaviour does not introduce new capabilities for an already authorized/unauthorized user. As any user with scp access already has SSH access, enabling direct command execution on the remote server.

As a workaround, customers are recommended to use SFTP (SSH File Transfer Protocol). SFTP is designed with better security mechanisms and is recommended by OpenSSH developers as a safer alternative.

Note: The CVE is disputed by the OpenSSH developers.

CVE-

2020-14145

5.9

5.7-8.6

8.7

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client).

NOTE: some reports state that 8.5 and 8.6 are also affected.

Not Impacted via Workaround

This vulnerability is specific to the manual initial connection attempts from the client side. These types of issues can be mitigated by using certificate-based connections.

Customers are recommended to use the “ssh host-certificate-file” config option from CLI to configure certificate-based hostkey algorithms.

The CVE is disputed by the OpenSSH developers.

CVE-2020-12062

7.5

8.2

8.3

The scp client in OpenSSH 8.2 incorrectly sends duplicate responses to the server upon a utimes system call failure, which allows a malicious unprivileged user on the remote server to overwrite arbitrary files in the client's download directory by creating a crafted subdirectory anywhere on the remote server.

The victim must use the command scp -rp to download a file hierarchy containing, anywhere inside, this crafted subdirectory. 

NOTE: the vendor points out that "this attack can achieve no more than a hostile peer is already able to achieve within the scp protocol" and "utimes does not fail under normal circumstances.

Not
Impacted

Junos OS/Junos OS Evolved is not shipped with the impacted OpenSSH version.

Hence, Junos OS/Junos OS Evolved are not impacted by the CVE.

CVE-2021-41617

7.0

6.2 - 8.7

8.8

The sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and

AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.

Not Impacted via Workaround

Neither AuthorizedKeysCommand nor AuthorizedPrincipalsCommand are enabled by default. Customers can apply a  workaround to prevent the issue by not configuring “authorized-keys-command” or “authorized-principals” under [ system services ssh ]  hierarchy.

Even if customers enable the feature, they must provide a script or program that is already wholly trusted. Customers should only specify a trusted program for either of these options.

CVE-

2021-28041

7.1

8.2 - 8.4

8.5

The “ssh-agent” in OpenSSH before 8.5 has a double free that may be relevant in a few less common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.

Not Impacted

Junos OS/Junos OS Evolved is not shipped with any of the impacted OpenSSH versions

Hence, Junos OS/Junos OS Evolved are not impacted by the
CVE.

CVE-

2021-

36368

3.7

<= 8.8

8.9

An issue was discovered in OpenSSH before 8.9. If a client is using public-key authentication with agent forwarding but without -oLogLevel=verbose, and an attacker has silently modified the server to support the None authentication option, then the user cannot determine whether FIDO (Fast Identity Online) authentication is going to confirm that the user wishes to connect to that server, or that the user wishes to allow that server to connect to a different server on the user's behalf. NOTE: the vendor's position is "this is not an authentication bypass, since nothing is being bypassed.

Not Impacted

This CVE is not considered applicable to Junos OS/Junos OS Evolved because FIDO authentication is not support by the SSH client in either OS.

CVE-

2023-38408

9.8

< 9.3p2

9.3p2

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. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

Not
Impacted

Junos OS/Junos OS Evolved CLI do not provide any SSH command to configure an option to allow agent forwarding.

The only way a user could be exposed to this vulnerability is by manually dropping to a Unix shell and connecting to a malicious host with agent-forwarding enabled in their session.

Customers are recommended to avoid initiating an SSH connection enabling agent forwarding using “-A” option from the shell.

Note: JUNOS OS Evolved does not use ssh-agent to manage the private keys. Hence this CVE is not applicable to JUNOS OS Evolved.

CVE-

2023-

28531

9.8

8.9 - 9.2

9.3

The “ssh-add” in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.

Not Impacted

Junos OS/Junos OS Evolved is not shipped with any of the impacted OpenSSH versions

Hence, Junos OS/Junos OS Evolved are not impacted by the CVE.

CVE-

2023-

48795

5.9

<= 9.5

9.6

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 negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers.

Not Impacted via Workaround

Junos OS/Junos OS Evolved can only be impacted when the ssh cipher list includes chacha20-poly135.

Furthermore, in Junos OS/Junos OS Evolved, chacha20-poly1305 has been hidden and deprecated as a default algorithm for sshd:

Junos OS: 19.4R3-S13, 20.4R3-S10, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.4R3-S1, 23.2R2, 23.4R2, 24.1R1, and all subsequent releases.

Junos OS Evolved: 19.4R3-S13, 20.4R3-S10, 21.4R3-S6, 22.1R3-S5, 22.2R3-S3, 22.4R3-S1, 23.2R2, 23.4R2, 24.1R1, and all subsequent releases.

Customers are recommended to either use one of the fixed releases mentioned above or not to use the ssh cipher option chacha20-poly135 at all.

For example, the following config is recommended best practice:

set system services ssh ciphers [[email protected] [email protected]]

You can find more information about this workaround in Juniper's knowledge base article JSA76462 [juniper.net]: [juniper.net]https://kb.juniper.net/JSA76462 [juniper.net] [juniper.net]

CVE-

2023-

51384

5.5

8.9- 9.5

9.6

In ssh-agent in OpenSSH before 9.6, certain destination constraints can be incompletely applied. When destination constraints are specified during addition of PKCS#11-hosted private keys, these constraints are only applied to the first key, even if a PKCS#11 token returns multiple keys.

Not Impacted

This does not impact Junos OS/Junos OS Evolved because it does not support the use of "ssh-agent" with destination constraints.

CVE-

2023-

51385

6.5

< 9.6

9.6

In ssh (SSH client program) in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.

Not Impacted

Junos OS/Junos OS Evolved are not impacted because the CLI does not expose the ProxyCommand option.

Customers are recommended not to (1) configure any SSH options using shell or (2) connect to any untrusted SSH hosts.

CVE-2024-6387

8.1

<4.4 and 8.6 to 9.7

9.8

A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead to 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.

Impacted

Junos OS has never been vulnerable to this issue. Junos OS prior to 24.2 is not affected by this vulnerability, and OpenSSH 9.7 implementation, used in Junos OS 24.2+, was patched to fix CVE-2024-6387.

Junos OS Evolved releases prior to 24.2 are not impacted as they

are not shipped with the impacted OpenSSH version.

Impacted Junos OS Evolved Release : “24.2R1, 24.2R1-S1”

Junos OS Evolved releases (24.2R1-S2 OR later) are either patched to fix CVE-2024-6387 OR they do not use the impacted OpenSSH version.

CVE-2024-39894

7.5

9.5-9.7

9.7

OpenSSH 9.5 through 9.7 before 9.8 sometimes allows timing attacks against echo-off password entry (e.g., for su and Sudo) because of an ObscureKeystrokeTiming logic error. Similarly, other timing attacks against keystroke entry could occur. 

Not Impacted

Junos OS/Junos OS Evolved have never included OpenSSH instance that is affected by CVE-2024-39894. Instances of OpenSSH 9.7p1 were always patched to fix CVE-2024-39894.

CVE-2024-7589

8.1

All supported versions of FreeBSD

FreeBSD releases: 13.3-RELEASE-p5,

14.0-RELEASE-p9, 14.1-RELEASE-p3

A signal handler in sshd(8) may call a logging function that is not async-signal-safe. The signal handler is invoked when a client does not authenticate within the LoginGraceTime seconds (120 by default). This signal handler executes in the context of the sshd(8)'s privileged code, which is not sandboxed and runs with full root privileges. This issue is another instance of the problem in CVE-2024-6387 addressed by FreeBSD-SA-24:04.openssh. The faulty code in this case is from the integration of blacklistd in OpenSSH in FreeBSD. As a result of calling functions that are not async-signal-safe in the privileged sshd(8) context, a race condition exists that a determined attacker may be able to exploit to allow an unauthenticated remote code execution as root. See FreeBSD-SA-24:08.openssh for details. 

Not Impacted

This CVE does not apply to Junos OS/Junos OS Evolved because no signal handler has ever had a call to a function that is not async-signal-safe.

CVE-2025-26466

5.9

9.5 to 9.9p1

9.9p2

A flaw was found in the OpenSSH package. For each ping packet the SSH server receives, a pong packet is allocated in a memory buffer and stored in a queue of packages. It is only freed when the server/client key exchange has finished. A malicious client may keep sending such packages, leading to an uncontrolled increase in memory consumption on the server side. Consequently, the server may become unavailable, resulting in a denial of service attack. 

Not Impacted via Workaround

Junos OS/Junos OS Evolved mitigates the reported vulnerability through a default configuration that limits pre authentication packets to 128.
Upon exceeding this threshold, connection requests are rejected, thus preventing potential denial-of-service attacks due to excessive memory consumption.  Customers can adjust this limit using the cli knob: set system services ssh max-pre-authentication-packets<value>
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/ssh-edit-system.html

CVE-2025-26465

6.8

6.9-9.8

9.9

A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.

Not Impacted

In Junos OS/Junos OS Evolved " VerifyHostKeyDNS " option is disabled by default. There is no configurable CLI option to configure DisableForwarding and it is disabled by default. Hence not affected.

CVE-2025-32728

4.3

7.4 – 9.9

10.0

In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.

Not Impacted

Junos OS/Junos OS Evolved does not use "DisableForwarding" option. There is no configurable CLI option to configure DisableForwarding and it is disabled by default. Hence not affected.

CVE-2025-61984

3.6

<= 10.0

10.1

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)

Not Impacted

Untrusted ssh:// URIs are never constructed

CVE-2025-61985

3.6

<= 10.0

10.1

ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.

Not Impacted

ProxyCommand is never used "%r" and the device never proxies to an untrusted host

CVE

CVSS v3 Scores

Impacted OpenSSH versions

Fixed

Open

SSH

version

Description

Impact to Junos OS or Junos OS Evolved

Solution/Workaround

CVE-2026-35385

8.1

<= 10.2

10.3

In OpenSSH before 10.3, a file downloaded by scp may be installed setuid or setgid, an outcome contrary to some users' expectations, if the download is performed as root with -O (legacy scp protocol) and without -p (preserve mode).

Not Impacted

The SCP legacy protocol preserves setuid/setgid bits on transferred files (confirmed reproducible). However, privilege escalation is blocked by platform integrity enforcement: veriexec in Junos and IMA in EVO.

CVE-2026-35386

8.1

<= 10.2

10.3

In OpenSSH before 10.3, command execution can occur via shell metacharacters in a username within a command line. This requires a scenario where the username on the command line is untrusted, and also requires a non-default configurations of % in ssh_config.

Not Impacted

Affected directives (Match exec, ProxyCommand, LocalCommand, KnownHostsCommand, RemoteCommand) are SSH client-side directives not exposed through the Junos CLI. Not present in shipped ssh_config.

CVE-2026-35387

6.5

<= 10.2

10.3

OpenSSH before 10.3 can use unintended ECDSA algorithms. Listing of any ECDSA algorithm in PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms is misinterpreted to mean all ECDSA algorithms.

Not Impacted

PubkeyAcceptedAlgorithms and HostbasedAcceptedAlgorithms are not configurable via CLI. All three ECDSA curves are accepted by default.

CVE-2026-35388

2.5

<= 10.2

10.3

OpenSSH before 10.3 omits connection multiplexing confirmation for proxy-mode multiplexing sessions.

Not Impacted

SSH multiplexing (ControlMaster/ControlPath) is not used or configurable on either platform. The vulnerable code path is never reached.

CVE-2026-35414

8.1

<= 10.2

10.3

OpenSSH before 10.3 mishandles the authorized_keys principals option in uncommon scenarios involving a principals list in conjunction with a Certificate Authority that makes certain use of comma characters.

Not Impacted

CLI-configured public keys are written as plain keys in authorized_keys - no support for cert-authority or principals="..." options. The vulnerable matching logic is never invoked.