Traffic disclosure via static-key TLS ciphers
Published Jan 15, 2026 · Updated Jan 15, 2026
Weak cryptography in Juniper Networks Junos Space before 24.1R5 allows man-in-the-middle attackers with server key material to read TLS traffic. The Apache HTTPS endpoint advertises and negotiates RSA static-key cipher suites instead of requiring ephemeral key exchange with Perfect Forward Secrecy. Exploitation requires an on-path position and access to the server's private key; recorded sessions can then be decrypted, while integrity and availability remain unaffected.
Summary
What happened
Weak cryptography in Juniper Networks Junos Space before 24.1R5 allows man-in-the-middle attackers with server key material to read TLS traffic. The Apache HTTPS endpoint advertises and negotiates RSA static-key cipher suites instead of requiring ephemeral key exchange with Perfect Forward Secrecy. Exploitation requires an on-path position and access to the server's private key; recorded sessions can then be decrypted, while integrity and availability remain unaffected.
The record
- CVE
- CVE-2026-21907
- Published
- Jan 15, 2026
- Updated
- Jan 15, 2026
- Vendor
- Juniper Networks
- Product
- Junos Space
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2026CVE publishedPublication date reported by the CVE source.
- Jan 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <24.1R5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo