CVE-2026-102022 Juniper Networks CVE debrief

Who should care

Network administrators responsible for Junos OS and Junos OS Evolved systems should assess exposure and take action to prevent potential disruptions to routing processes. This includes verifying affected versions, applying patches or mitigations, and restricting access to configured BGP-LS peers to trusted sources only. The vulnerability can impact network availability and reliability, and administrators should prioritize patching or mitigating this issue.

Why it matters

Network administrators responsible for Junos OS and Junos OS Evolved systems should assess exposure and take action to prevent potential disruptions to routing processes. This vulnerability requires verification of affected versions and application of patches or mitigations to prevent exploitation.

• Potential disruption to routing processes.
• Need to verify and patch or mitigate vulnerable systems.
• Possible impact on network availability and reliability.

Technical summary

A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker with access to a configured BGP-LS peer to cause an rpd crash via a crafted BGP-LS Link NLRI advertisements. The vulnerability requires verification of affected versions and application of patches or mitigations to prevent exploitation. The attack can be performed via crafted BGP-LS Link NLRI advertisements, and network administrators should be aware of the potential disruption to routing processes.

Defensive priority

Network administrators should prioritize patching or mitigating this vulnerability to prevent potential disruptions to routing processes.

Recommended defensive actions

• Network administrators should assess exposure and apply patches or mitigations to prevent potential disruptions to routing processes.
• Verify that BGP-LS traffic-engineering is not enabled on untrusted interfaces.
• Restrict access to configured BGP-LS peers to trusted sources only.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE Program record and NVD vulnerability detail provide information on this vulnerability. A vendor advisory is available from Juniper Networks. The vulnerability requires verification of affected versions and application of patches or mitigations to prevent exploitation. The evidence is limited to the provided CVE record and vendor advisory, and further verification is needed to confirm the affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.