CVE-2026-33801 in Junos OS
Summary
by MITRE • 07/10/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 adjacent, unauthenticated attacker sending a specific BGP update over an established BGP session to cause a Denial-of-Service (DoS).
Upon receipt of a specifically malformed non-inet/inet6 unicast BGP update, an RPD crash and restart is triggered, which will cause a complete service outage until routing has reconverged. The rpd crash occurs before the update can be readvertised, so there is no downstream propagation.
This issue affects:
* Junos OS versions 25.2 before 25.2R2;
* Junos OS Evolved versions 25.2 before 25.2R2-EVO.
This issue doesn't affect Junos OS versions before 25.2R1 nor Junos OS Evolved versions before 25.2R1-EVO.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 07/10/2026
The vulnerability under consideration represents a critical improper check for unusual or exceptional conditions flaw within the routing protocol daemon of juniper networks junos os and junos os evolved platforms. this weakness manifests specifically in how the rpd process handles certain malformed bgp updates, creating a significant denial-of-service vector that can disrupt network operations. the issue is particularly concerning as it requires minimal attacker privileges to exploit, needing only an adjacent network position and an established bgp session to execute successfully.
the technical implementation of this vulnerability stems from inadequate validation mechanisms within the rpd daemon's handling of non-inet/inet6 unicast bgp updates. when a specifically crafted malformed update is received, the daemon fails to properly validate the update structure before processing it, leading to an abrupt crash and subsequent restart of the routing protocol daemon. this failure mode occurs at a critical processing stage where the update has been accepted but not yet validated for proper format or content, allowing the malformed data to trigger an internal exception that terminates the process entirely.
the operational impact of this vulnerability extends beyond simple service disruption to encompass complete network outage conditions until routing protocols reconverge. during the crash and restart cycle, all routing information becomes temporarily unavailable, causing significant network instability and potentially affecting multiple services dependent on proper routing functionality. the timing of the crash is particularly problematic as it occurs before any update can be readvertised to downstream peers, meaning that the malformed update cannot propagate through the network and cause additional disruptions beyond the immediate affected device.
this vulnerability aligns with common weakness enumeration standard cwe-252 which categorizes improper checks for unusual conditions as a fundamental flaw in defensive programming practices. from an attack perspective, this issue maps directly to the mitre attack framework's privilege escalation and denial of service tactics, where the minimal attack requirements make it particularly dangerous in operational environments. the exploitability characteristics indicate that network proximity is sufficient to trigger the vulnerability, making it accessible to attackers within the same broadcast domain or adjacent network segments.
the affected versions represent a specific timeframe where this validation gap was present in both standard junos os and the evolved variant, with version 25.2R1 and earlier being unaffected due to implementation changes that likely included enhanced input validation routines. network administrators should recognize that this vulnerability affects routing operations specifically within the bgp update processing pipeline, which forms a critical component of internet connectivity for most enterprise and service provider networks. the lack of authentication requirements means that any device with access to an established bgp session can potentially trigger this condition without requiring additional credentials or elevated privileges.
mitigation strategies should prioritize immediate deployment of vendor patches addressing the specific validation deficiencies in the rpd daemon's handling of malformed updates. network security teams should implement monitoring solutions to detect unusual bgp update patterns and establish automated alerting for potential exploitation attempts. operational procedures should include regular testing of routing protocol resilience and development of incident response protocols specifically addressing bgp daemon crashes and subsequent reconvergence periods. organizations should also consider implementing network segmentation strategies to limit the scope of potential impact from such vulnerabilities, particularly in critical infrastructure environments where uninterrupted routing operations are essential for maintaining service availability.