An Incomplete List of Disallowed Inputs vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS).

When in a BGP traffic engineering scenario a specific, valid, optional, non-transitive BGP update is received over an established BGP session, RPD crashes and automatically restarts, which leads to traffic impact until routing has reconverged.

This issue affects:
Junos OS:

• All versions before 23.2R2-S6;
• 23.4 versions before 23.4R2-S7;
• 24.2 versions before 24.2R2-S4;
• 24.4 versions before 24.4R2-S4;
• 25.2 versions before 25.2R1-S2, 25.2R2;

Junos OS Evolved:

• All versions before 23.2R2-S6-EVO;
• 23.4 versions before 23.4R2-S8.11-EVO;
• 24.2 versions before 24.2R2-S4-EVO;
• 24.4 versions before 24.4R2-S5-EVO;
• 25.2 versions before 25.2R1-S2-EVO, 25.2R2-EVO;

To be exposed to this issue the system needs to be configured with:

[ protocols bgp ... family traffic-engineering ]

[ policy-options policy-statement <name> from family traffic-engineering ]

[ policy-options policy-statement <name> from family traffic-engineering then accept ]

[ protocols mpls traffic-engineering database export policy <name> ]


Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

This issue was seen during production usage.

This issue has been assigned CVE-2026-102087.

The following software releases have been updated to resolve this specific issue: Junos OS: 23.2R2-S6, 23.4R2-S7, 24.2R2-S4, 24.4R2-S4, 25.2R1-S2, 25.2R2, 25.4R1, and all subsequent releases; Junos OS Evolved: 23.2R2-S6-EVO, 23.4R2-S8.11-EVO, 24.2R2-S4-EVO, 24.4R2-S5-EVO, 25.2R1-S2-EVO, 25.2R2-EVO, 25.4R1-EVO, and all subsequent releases. Note: For Junos OS releases 23.2, 23.4, and 24.2, and Junos OS Evolved releases 23.2-EVO, 23.4-EVO, and 24.2-EVO, specific respins have been referenced. Previously published versions of these releases have been rebuilt to resolve the security vulnerabilities identified in this advisory.

This issue is being tracked as 1908614 which is visible on the Customer Support website.

Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

There are no known workarounds for this issue.

2026-10-14: Initial Publication

• KB16613: Overview of the Juniper Networks SIRT Quarterly Security Bulletin Publication Process [juniper.net]
• KB16765: In which releases are vulnerabilities fixed? [juniper.net]
• KB16446: Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories [juniper.net]
• Report a Security Vulnerability - How to Contact the Juniper Networks Security Incident Response Team