CVE-2026-21907 Details
Description
A Use of a Broken or Risky Cryptographic Algorithm vulnerability in the TLS/SSL server of Juniper Networks Junos Space allows the use of static key ciphers (ssl-static-key-ciphers), reducing the confidentiality of on-path traffic communicated across the connection. These ciphers also do not support Perfect Forward Secrecy (PFS), affecting the long-term confidentiality of encrypted communications.This issue affects all versions of Junos Space before 24.1R5.
A vulnerability in the TLS/SSL server of Juniper Networks Junos Space, present in all versions prior to 24.1R5, allows the use of static key ciphers. This reduces the confidentiality of on-path traffic and does not support Perfect Forward Secrecy, impacting the long-term confidentiality of encrypted communications.
Users can upgrade to Junos Space version 24.1R5 or later to address this vulnerability. Ensure that any clients connecting to the device do not allow negotiation of static RSA key exchange.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 15, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://kb.juniper.net/JSA106006 | [email protected] | Vendor Advisory |
| https://supportportal.juniper.net/JSA106006 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-327 | Use of a Broken or Risky Cryptographic Algorithm | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| juniper junos space | < 24.1 24.1 r1 24.1 r2 24.1 r3 24.1 r4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 23, 2026 | Initial Analysis | [email protected] |
| Jan 15, 2026 | New CVE Received | [email protected] |