CVE-2025-60011 in Junos OSinfo

Summary

by MITRE • 01/15/2026

An Improper Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an availability impact for downstream devices.

When an affected device receives a specific optional, transitive BGP attribute over an existing BGP session, it will be erroneously modified before propagation to peers. When the attribute is detected as malformed by the peers, these peers will most likely terminate the BGP sessions with the affected devices and thereby cause an availability impact due to the resulting routing churn.

This issue affects:

Junos OS:



* all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5 * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S2, * 24.4 versions before 24.4R2;




Junos OS Evolved: 



* all versions before 22.4R3-S8-EVO, * 23.2 versions before 23.2R2-S5-EVO, * 23.4 versions before 23.4R2-S6-EVO, * 24.2 versions before 24.2R2-S2-EVO, * 24.4 versions before 24.4R2-EVO.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 01/16/2026

The vulnerability CVE-2025-60011 represents a critical weakness in the routing protocol daemon rpd of Juniper Networks Junos OS and Junos OS Evolved systems, classified under CWE-252 Improper Check for Unusual or Exceptional Conditions. This flaw exists within the BGP routing protocol implementation where the system fails to properly validate optional transitive BGP attributes received over existing sessions. The vulnerability stems from insufficient input validation mechanisms that allow malformed attributes to be processed and subsequently propagated to neighboring devices without proper error handling or sanitization.

The technical exploitation of this vulnerability occurs when an attacker sends specifically crafted optional BGP attributes to an affected device through an existing BGP session. The rpd daemon incorrectly modifies these attributes before forwarding them to peers, creating a scenario where downstream devices receive malformed data that violates BGP protocol specifications. This improper handling triggers a cascade of failures as peer devices detect the malformed attributes and respond by terminating their BGP sessions with the affected system. The resulting session termination creates significant routing instability and network disruption.

From an operational impact perspective, this vulnerability creates a substantial availability risk for downstream network devices and the overall routing infrastructure. The termination of BGP sessions leads to routing churn, where network paths are repeatedly recalculated and re-established, causing temporary or extended network outages. The cascading effect can propagate across multiple network segments, potentially affecting large portions of the routed network infrastructure. This vulnerability particularly impacts network stability during peak traffic periods when routing convergence is most critical, making it a high-priority concern for network operators.

Network security professionals should implement immediate mitigations including applying the relevant software patches released by Juniper Networks, which address the specific validation issues in the rpd daemon. Additional protective measures include implementing BGP session monitoring and alerting systems to detect abnormal session termination patterns, deploying BGP attribute filtering to reject suspicious optional attributes, and configuring session timers to minimize the impact of session disruptions. Organizations should also consider implementing network segmentation and redundancy measures to isolate affected routing domains and maintain network availability during remediation efforts. The vulnerability aligns with ATT&CK technique T1562.007 for Impairing Availability and demonstrates the importance of proper input validation in network protocol implementations as outlined in the NIST Cybersecurity Framework.

Responsible

Juniper

Reservation

09/23/2025

Disclosure

01/15/2026

Moderation

accepted

CPE

ready

EPSS

0.00020

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!