High priorityDisclosed

Advisory · CVE-2026-102022

Reachable assertion in Junos rpd lets a BGP-LS peer crash it with a crafted Link NLRI

A reachable assertion vulnerability in the routing protocol daemon (rpd) of Junos OS and Junos OS Evolved lets an attacker with access to a configured BGP-LS peer cause an rpd crash via crafted BGP-LS Link NLRI advertisements. Juniper rates it CVSS 4.0 8.7 (CVSS 3.1 7.5).

Vendor
Juniper Networks
Product
Junos OS
Identifier / CWE
CVE-2026-102022
CWE-617
Action timing
Immediate
ELI5

Explain it like I’m five

One crafted link advertisement is enough to assert the daemon into restarting.

SIMPLIFIED_ATTACK_PATH03 STEPS
  1. 01Trigger input

    An attacker sends the crafted protocol traffic described for CVE-2026-102022.

  2. 02Weakness trips

    The daemon mishandles the input through the reachable assertion weakness.

  3. 03Impact lands

    The routing or control-plane daemon crashes or misbehaves as described.

What happened

Juniper disclosed CVE-2026-102022 in its October 2026 security release: a reachable assertion vulnerability (CWE-617) in rpd. Crafted BGP-LS Link NLRI advertisements from a configured peer can crash rpd. The vendor record lists affected releases starting with the 24.4 line.

Juniper’s JSA112187 lists the affected service releases and the October 2026 service release thresholds that carry the fix. Match your exact release to the advisory rather than guessing here.

What to do

  1. Inventory every Junos OS deployment, including test, training, and individually managed instances.
  2. Apply the vendor fix or upgrade exactly as directed in the linked vendor bulletin or advisory.
  3. Restrict network access to Junos OS while remediation is underway, especially for internet-facing instances.
  4. Review application and server logs for rpd crashes following BGP-LS Link NLRI advertisements from configured peers.
  5. Check for accounts, content, or configuration created outside normal change processes, and rotate exposed credentials where access cannot be ruled out.
  6. Verify the deployed version or patch level after remediation.

Management note

Companion to CVE-2026-102020 in the same BGP-LS code. Patch together and watch controller sessions after.