CVE-2026-102179 Juniper Networks CVE debrief

Who should care

Network administrators and operators using Juniper Networks Junos OS and Junos OS Evolved should assess their exposure and prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks on their routing infrastructure.

Why it matters

Network administrators and operators should prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks on their routing infrastructure. This vulnerability requires verification from official sources to determine affected versions, exploitation, and remediation.

• Potential denial-of-service attacks on routing infrastructure
• Interruption of routing protocols until the daemon restarts and reconverges
• Crash of the routing protocol daemon (rpd)

Technical summary

The vulnerability is caused by an Out-of-bounds Write in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved. This allows an attacker with access to a configured BGP EVPN peer to cause a denial of service via BGP EVPN route processing when the l2vpn-evpn RIB telemetry sensor is subscribed. The vulnerability requires verification from official sources to determine affected versions, exploitation, and remediation. Successful exploitation can crash rpd and interrupt routing protocols until the daemon restarts and reconverges.

Defensive priority

Network administrators should prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks on their routing infrastructure.

Recommended defensive actions

• Network administrators should review and apply patches for affected Junos OS and Junos OS Evolved versions.
• Administrators should consider disabling BGP EVPN RIB telemetry if not required.
• Network operators should monitor their routing infrastructure for potential disruptions.
• Network administrators should assess their exposure and prioritize patching or mitigating this vulnerability to prevent potential denial-of-service attacks on their routing infrastructure.
• Network administrators should review compensating controls for exposed systems while remediation is scheduled and verified.
• Network operators should check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Network administrators should track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and potential impact. However, there is limited information on the exploitability of the vulnerability and no reported instances of exploitation.

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.