High priorityDisclosed

Advisory · CVE-2026-102026

Resource lifetime flaw in Junos rpd lets an eBGP peer crash it with RIB sharding on

An improper control of a resource through its lifetime vulnerability in the routing protocol daemon (rpd) of Junos OS and Junos OS Evolved lets an adjacent eBGP peer cause a routing-daemon crash via a BGP route update when RIB sharding is enabled. Juniper rates it CVSS 4.0 8.7 (CVSS 3.1 7.5).

Advisory published October 14, 2026Independent summary
Vendor
Juniper Networks
Product
Junos OS
Identifier / CWE
CVE-2026-102026
CWE-664
Action timing
Immediate
ELI5

Explain it like I’m five

RIB sharding spreads routing work across threads; a lifetime mix-up lets a peer update crash the whole daemon anyway.

SIMPLIFIED_ATTACK_PATH03 STEPS
  1. 01Trigger input

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

  2. 02Weakness trips

    The daemon mishandles the input through the improper control of a resource through its lifetime weakness.

  3. 03Impact lands

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

What happened

Juniper disclosed CVE-2026-102026 in its October 2026 security release: an improper control of a resource through its lifetime (CWE-664) in rpd. An adjacent eBGP peer can crash the routing daemon via a BGP route update when RIB sharding is enabled.

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 on devices with RIB sharding enabled, following eBGP route updates.
  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

Performance features change code paths, not threat models. Patch sharded and unsharded routers alike.