CVE-2026-21907: Junos Space: TLS/SSL server supports use of static key ciphers (ssl-static-key-ciphers)

Published Jan 15, 2026
·
Updated

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.

Affected Software

6 affected components
Juniper Networks Junos Space<24.1R5
Juniper Junos Space<24.1
Juniper Junos Space=24.1-r1
Juniper Junos Space=24.1-r2
Juniper Junos Space=24.1-r3
Juniper Junos Space=24.1-r4

Remediation

Information

The following software releases have been updated to resolve this specific issue: Junos Space 24.1R5 and all subsequent releases.

Event History

Jan 15, 2026
CVE Published
via MITRE·08:21 PM
Data Sourced
via MITRE·08:21 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Feb 19, 58052
Event
via FIRST·01:23 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21907?

CVE-2026-21907 has a high severity due to its vulnerability in the use of static key ciphers in TLS/SSL, compromising data confidentiality.

2

How do I fix CVE-2026-21907?

To fix CVE-2026-21907, disable the use of static key ciphers in the Junos Space TLS/SSL configuration.

3

What systems are affected by CVE-2026-21907?

CVE-2026-21907 affects Juniper Networks Junos Space versions up to 24.1R5.

4

What are the risks associated with CVE-2026-21907?

The risks associated with CVE-2026-21907 include potential data breaches and loss of confidentiality due to the use of broken cryptographic algorithms.

5

Is there a workaround for CVE-2026-21907?

A workaround for CVE-2026-21907 is to avoid using static key ciphers within the TLS/SSL configuration until a patch can be applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203