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

Published Jan 27, 2026
·
Updated

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.

Affected Software

3 affected components
Juniper Networks Session Smart Router>=undefined, <5.6.17, >=undefined, <6.0.8, >=undefined, <6.1.12-lts, >=undefined, <6.2.8-lts, >=undefined, <6.3.3-r2
Juniper Networks Session Smart Conductor>=undefined, <5.6.17, >=undefined, <6.0.8, >=undefined, <6.1.12-lts, >=undefined, <6.2.8-lts, >=undefined, <6.3.3-r2
Juniper Networks WAN Assurance Managed Routers>=undefined, <5.6.17, >=undefined, <6.0.8, >=undefined, <6.1.12-lts, >=undefined, <6.2.8-lts, >=undefined, <6.3.3-r2

Remediation

Information

The following software releases have been updated to resolve this issue: Session Smart Router: SSR-5.6.17, SSR-6.1.12-lts, SSR-6.2.8-lts, SSR-6.3.3-r2 and subsequent releases. It is suggested to upgrade all affected systems to one of these versions of software. In a Conductor-managed deployment, it is sufficient to upgrade only the Conductor nodes and the fix will be applied automatically to all connected routers. As practical, the routers should still be upgraded to a fixed version however they will not be vulnerable once they connect to an upgraded Conductor. Router patching can be confirmed once the router reaches the “running" (on 6.2 and earlier) or “synchronized” (on 6.3+) state on the Conductor".   This vulnerability has been patched automatically on devices that operate with WAN Assurance (where configuration is also managed) connected to the Mist Cloud. As practical, the routers should still be upgraded to a version containing the fix. It is important to note that when the fix is applied automatically on routers managed by a Conductor or on WAN assurance, it will have no impact on data-plane functions of the router. The application of the fix is non-disruptive to production traffic. There may be a momentary downtime (less than 30 seconds) to the web-based management and APIs.

Event History

Feb 18, 2025
News Published
via BleepingComputer·05:07 PM
News Published
via BleepingComputer·05:08 PM
Jan 27, 2026
CVE Published
via MITRE·08:32 PM
Data Sourced
via MITRE·08:32 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness

Peer vulnerabilities

Found alongside the following vulnerabilities.

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-2025-21589?

CVE-2025-21589 is classified as a critical vulnerability due to its potential to allow attackers to bypass authentication on affected Juniper devices.

2

How do I fix CVE-2025-21589?

To resolve CVE-2025-21589, update affected devices to the latest firmware version provided by Juniper Networks.

3

Which products are affected by CVE-2025-21589?

CVE-2025-21589 affects Juniper Networks Session Smart Router, Session Smart Conductor, and WAN Assurance Managed Routers.

4

Can exploiting CVE-2025-21589 lead to a full system compromise?

Yes, exploiting CVE-2025-21589 can allow an attacker to gain administrative access, potentially leading to a full system compromise.

5

Is there a workaround for CVE-2025-21589 if I cannot update immediately?

Currently, there's no known workaround for CVE-2025-21589, so updating to a secure version is strongly recommended.

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