CVE 9.8 CRITICAL

Session Smart Router, Session Smart Conductor, WAN Assurance Router: API Authentication Bypass vulnerability_CVE-2025-21589

9.8 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Description

An Authentication Bypass Using an
Alternate Path or Channel vulnerability in Juniper Networks Session Smart
Router may allows a network-based attacker to bypass authentication
and take administrative control of the device.

This issue affects Session Smart Router: 



* from 5.6.7 before 5.6.17, 
* from 6.0 before 6.0.8 (affected from 6.0.8),

* from 6.1 before 6.1.12-lts, 
* from 6.2 before 6.2.8-lts, 
* from 6.3 before 6.3.3-r2; 




This issue affects Session Smart Conductor: 



* from 5.6.7 before 5.6.17, 
* from 6.0 before 6.0.8 (affected from 6.0.8),

* from 6.1 before 6.1.12-lts, 
* from 6.2 before 6.2.8-lts, 
* from 6.3 before 6.3.3-r2; 




This issue affects WAN Assurance Managed Routers: 



* from 5.6.7 before 5.6.17, 
* from 6.0 before 6.0.8 (affected from 6.0.8),

* from 6.1 before 6.1.12-lts, 
* from 6.2 before 6.2.8-lts, 
* from 6.3 before 6.3.3-r2.

Basic Information

ID CVE-2025-21589
Source juniper
Published Jan 27, 2026 at 20:32
Modified Jan 27, 2026 at 21:28

Affected Product

Vendor Juniper Networks
Product Session Smart Router
Version 5.6.7
Affected Versions Juniper Networks Session Smart Router 5.6.7
Juniper Networks Session Smart Router 6.1
Juniper Networks Session Smart Router 6.2
Juniper Networks Session Smart Router 6.3
Juniper Networks Session Smart Conductor 5.6.7
Juniper Networks Session Smart Conductor 6.1
Juniper Networks Session Smart Conductor 6.2
Juniper Networks Session Smart Conductor 6.3
Juniper Networks WAN Assurance Managed Router 5.6.7
Juniper Networks WAN Assurance Managed Router 6.1
Juniper Networks WAN Assurance Managed Router 6.2
Juniper Networks WAN Assurance Managed Router 6.3

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.