PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-102024 Juniper Networks CVE debrief

An Integer Overflow or Wraparound vulnerability in the routing daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated BGP peer to cause a denial of service via BGP route updates when extended-nexthop-tunnel is enabled. This vulnerability affects network operations by potentially causing a routing daemon crash, which can disrupt network stability and availability. Network administrators should assess exposure and prioritize patching to mitigate potential impacts.

Vendor
Juniper Networks
Product
Junos OS
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-14
Original CVE updated
2026-10-16
Advisory published
2026-10-14
Advisory updated
2026-10-16

Who should care

Network administrators and security teams responsible for managing Junos OS and Junos OS Evolved systems should assess exposure and prioritize patching. They should also verify and apply security updates from Juniper Networks, restrict exposure of vulnerable systems to untrusted BGP peers, and review compensating controls for exposed systems.

Why it matters

CVE-2026-102024 is a high-severity vulnerability in Junos OS and Junos OS Evolved that can cause a denial of service. Network administrators should prioritize patching and verify exposure.

  • Potential denial of service via routing daemon crash
  • Need to verify and apply security updates from Juniper Networks
  • Possible exposure of vulnerable systems to untrusted BGP peers

Technical summary

The vulnerability exists in the routing daemon (rpd) of Junos OS and Junos OS Evolved. An authenticated BGP peer can cause a denial of service by sending BGP route updates when extended-nexthop-tunnel is enabled. This can lead to a routing daemon crash, disrupting network operations. The vulnerability is caused by an Integer Overflow or Wraparound condition in the routing daemon, which can be exploited by an authenticated BGP peer. Network administrators should prioritize patching vulnerable systems, especially those exposed to untrusted BGP peers.

Defensive priority

Network administrators should prioritize patching vulnerable Junos OS and Junos OS Evolved systems, especially those exposed to untrusted BGP peers.

Recommended defensive actions

  • Patch vulnerable Junos OS and Junos OS Evolved systems
  • Verify and apply Juniper Networks' security updates
  • Restrict exposure of vulnerable systems to untrusted BGP peers
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE Program record and NVD vulnerability detail provide information on the Integer Overflow or Wraparound vulnerability in Junos OS and Junos OS Evolved. A vendor advisory from Juniper Networks is also available. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify exposure and apply patches according to vendor guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-102024 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-102024

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-102024 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-102024

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.