Skip to content
major vulnerability· requires attention

Affects Juniper Junos (widely deployed network core OS); adjacency exploit can crash routing daemon and disrupt network infrastructure at scale.

Networks

CVE-2026-102026

8.7
High
EPSS 0.46%Oct 17, 2026

Adjacent eBGP peer can crash Junos rpd via crafted BGP update with RIB sharding.

common questions

Is CVE-2026-102026 being exploited?

Not confirmed. CVE-2026-102026 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-102026?

CVE-2026-102026 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-102026?

Not known from our data. No patch reference has been recorded for CVE-2026-102026, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-102026 affect?

CVE-2026-102026 affects Juniper Junos OS (rpd), Juniper Junos OS Evolved (rpd). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-102026?

Follow Juniper advisory; restrict/unpeer untrusted eBGP peers, consider disabling RIB sharding, apply vendor fix when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Juniper Junos OS (rpd)Juniper Junos OS Evolved (rpd)
impact

Adjacent eBGP peer can crash rpd causing routing-daemon outage and network routing disruption/DoS.

action required

Immediate action required

affected versions
Juniper Networks Junos OS
  • affected< 23.2R2-S7.7
  • affected>= 23.4 and < 23.4R2-S8.13
  • affected>= 24.2 and < 24.2R2-S5.5
  • affected>= 24.4 and < 24.4R2-S5
  • affected>= 25.2 and < 25.2R2-S2
  • affected>= 25.4 and < 25.4R1-S3
  • affected>= 26.2 and < 26.2R1-S2
vendor says fixed in< 22.1R1
Juniper Networks Junos OS Evolved
  • affected< 23.2R2-S7.7-EVO
  • affected>= 23.4 and < 23.4R2-S8.11-EVO
  • affected>= 24.2 and < 24.2R2-S5.6-EVO
  • affected>= 24.4 and < 24.4R2-S5-EVO
  • affected>= 25.2 and < 25.2R2-S2-EVO
  • affected>= 25.4 and < 25.4R1-S3-EVO
  • affected>= 26.2 and < 26.2R1-S2-EVO
  • affected23.4X100
  • affected>= 25.2X100 and < 25.2X100-D35-EVO
  • affected>= 25.4X300 and < 25.4X300-D40-EVO
vendor says fixed in< 22.1R1-EVO

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free