Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish BGP session with target
-
ExploitAdvertise malformed SRv6 service route
-
ExecutionTrigger improper quantity validation in rpd
-
ImpactCrash rpd and disrupt routing
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Input size validation
|
| Exploitation Conditions | Exploitation requires that SRv6 dynamic tunnels be explicitly enabled on the device (a non-default feature configuration) AND that the attacker hold an established BGP peering session with the target, from which a malformed BGP-signaled SRv6 service route can be advertised. These two preconditions are the primary limiting factors: devices without SRv6 dynamic tunnels configured, or without a BGP session reachable by the attacker, are not exposed. There is no user-interaction or credential requirement (PR:N/UI:N) once a BGP adjacency exists, so any neighbor able to send routes to the affected rpd can trigger the crash; impact is limited to availability (routing daemon crash and routing disruption). |
| Impact | This is a credible but conditional denial-of-service issue, not a code-execution or data-breach risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) shows a network-reachable, low-complexity, unauthenticated trigger, but the impact is confined to availability (VA:H, with SA:L for routing fallout) - confidentiality and integrity are untouched (VC:N/VI:N). The 8.7 score is driven almost entirely by the availability impact on a core routing component (rpd), so treat it as a high-impact-but-scoped outage risk rather than a system-compromise risk. Crucially, real-world exposure is gated by two preconditions the raw score does not reflect: SRv6 dynamic tunnels must be enabled, and the attacker must already be an established BGP peer. No EPSS score, KEV listing, or public POC was provided, and no public exploit identified at time of analysis - so there is no evidence of active or imminent widespread exploitation. The PR:N rating is technically correct (BGP has no user authentication) but understates the trust precondition: only a configured, established BGP neighbor can deliver the malformed route, which in practice limits the realistic attacker set to peers/adjacent networks. Priority should be high for operators running SRv6 dynamic tunnels at network edges with external BGP peers, and low-to-moderate for everyone else. |
| Exploit ScenarioDerived | An attacker who controls or compromises a BGP neighbor of a Junos OS/Junos OS Evolved device that has SRv6 dynamic tunnels enabled advertises a specially malformed BGP-signaled SRv6 service route. The rpd routing daemon fails to properly validate a quantity field in the input and crashes, dropping routing adjacencies and disrupting traffic forwarding. No public exploit identified at time of analysis, and because the trigger is low-complexity once a BGP session exists, repeated advertisements can produce a sustained denial of service. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Oct 14, 2026
A malformed BGP-signaled SRv6 service route can crash the routing protocol daemon (rpd) on Juniper Networks Junos OS and Junos OS Evolved, causing a denial of service that disrupts routing on the affected device. The issue is remotely triggerable with no credentials or user interaction (CVSS:4.0 AV:N/AC:L/AT:N/PR:N/UI:N, VA:H), scoring 8.7, but it is conditional: exploitation requires that SRv6 dynamic tunnels be explicitly enabled (a non-default configuration) and that the attacker already hold an established BGP peering session with the target. Impact is limited to availability of the routing daemon - there is no confidentiality or integrity impact - and no public exploit has been identified at time of analysis. All software versions enumerated by the vendor are unpatched; Juniper has released fixed builds.
Earlier versions of this analysis (2)
Denial of service in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved lets a remote BGP peer crash the daemon by sending a malformed BGP-signaled SRv6 service route. The CVSS v4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) confirms this is exploitable by unauthenticated remote attackers with no user interaction, resulting in a high availability impact; the vendor scores it 8.7 while an independent v3.1 assessment rates it 7.5 (C:N/I:N/A:H). Reach is gated by configuration: SRv6 dynamic tunnels must be explicitly enabled and the attacker must already hold an accepted BGP peering position, so routers without that feature or without untrusted peers are not exposed. No public exploit code has been identified and this CVE is not reported as confirmed actively exploited (CISA KEV).
Denial of service in Juniper Networks Junos OS and Junos OS Evolved lets a remote, unauthenticated BGP peer crash the routing protocol daemon (rpd) by sending a malformed BGP-signaled SRv6 service route. The root cause is an improper validation of a specified quantity in input (CWE-1284) in rpd's SRv6 service-route handling, and the CVSS 3.1 base of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects a network-reachable, low-complexity, availability-only impact with no confidentiality or integrity loss. Exploitation is gated by two prerequisites: SRv6 dynamic tunnels must be explicitly enabled (non-default, segment-routing-specific configuration), and the attacker must already hold an established BGP peering session - i.e., a routing-adjacency trust relationship rather than arbitrary remote access. No public exploit code and no confirmed active exploitation were identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to Junos OS 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, or 26.2R1-S2 (or later on each train), and to Junos OS Evolved 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.4R1-S3-EVO, or 26.2R1-S2-EVO, with the associated maintenance builds 25.2X100-D35-EVO and 25.4X300-D40-EVO for the X-release branches; consult JSA112187 at https://supportportal.juniper.net/JSA112187 for the definitive per-train fix matrix before scheduling maintenance. Where upgrading cannot be done immediately, the most effective compensating control is to disable SRv6 dynamic tunnels on the device, which removes the vulnerable code path entirely - the trade-off being loss of the SRv6 dynamic-tunnel service that the configuration was providing. Because the attacker must already hold a BGP adjacency, restricting eBGP and iBGP peering to explicitly trusted, authenticated neighbors (TCP-MD5/TCP-AO or GTSM TTL security, and inbound prefix/attribute filtering such as rejecting unexpected SRv6 service-route AFI/SAFI advertisements) materially reduces exposure, at the cost of additional peering configuration and possible session-establishment friction with untrusted or transient peers. There is no vendor-confirmed mitigation that preserves SRv6 dynamic tunnels while eliminating the crash, so the disable-or-upgrade choice is the practical decision point; note also that rpd crashes cause session resets and reconvergence, so monitoring rpd restarts and BGP flaps can serve as a detection signal.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is classified as CWE-1284 (Improper Validation of Specified Quantity in Input) and resides in rpd, the Junos routing protocol daemon that handles BGP and other routing protocols. When SRv6 dynamic tunnels are enabled, rpd processes BGP-signaled SRv6 service routes and fails to correctly validate a quantity field carried in the route - an SRv6 SID or service-route length/count attribute that is not bounds-checked before use. A neighbor able to advertise a malformed route over an established BGP session therefore drives rpd into a fatal condition, terminating the daemon and disrupting all routing processes it manages. The flaw affects both the classic FreeBSD-based Junos OS and the Linux-based Junos OS Evolved code lines, as reflected in the CPE entries (cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved). The relevant attack surface is Segment Routing over IPv6 (SRv6) service-route signaling - a newer, optional feature - rather than base BGP or standard IPv6 forwarding, which is why the exposure is configuration-dependent rather than universal.
Know when Junos Os gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
Network-reachable malformed BGP route from an unauthenticated peer (AV:N/PR:N/AC:L); impact is a routing-daemon crash so availability-only (A:H), no C/I impact.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
An Improper Validation of Specified Quantity in Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a remote unauthenticated BGP peer to cause an rpd crash via a malformed BGP-signaled SRv6 service route when SRv6 dynamic tunnels are enabled.
Executive ViewAI
Juniper Networks Junos OS and Junos OS Evolved are affected by a high-severity vulnerability (CVE-2026-102065) that allows an unauthenticated remote attacker to crash the routing protocol daemon via a malformed BGP-signaled SRv6 service route, causing a denial-of-service condition that disrupts routing on the device. Exploitation requires SRv6 dynamic tunnels to be explicitly enabled (a non-default configuration) and an established BGP peering session, which narrows the attack surface but still poses significant risk to organizations with that setup. Leadership should prioritize patching because routing outages can cascade into broader network and business service disruptions.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u
Unauthenticated remote code execution with root privileges affects Juniper Networks Junos OS devices that expose the J-W
Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow
A stack-based buffer overflow in the srxpfe packet forwarding process of Juniper Networks Junos OS on SRX Series devices
Unauthenticated remote code execution with elevated privileges is possible in Juniper Junos OS and Junos OS Evolved thro
Remote root code execution in the routing protocol daemon (rpd) of Juniper Junos OS is reachable through protocol-valid
Remote code execution (on Junos OS) and rpd denial of service (on Junos OS and Junos OS Evolved) result from a stack-bas
Remote code execution with root privileges on Juniper Networks Junos OS and Junos OS Evolved is possible when the routin
Remote code execution and denial of service in Juniper Networks Junos OS and Junos OS Evolved arise from a stack-based b
Unauthenticated remote attackers can gain root-level configuration access and fully compromise Juniper Junos OS and Juno
Integer underflow in the Junos OS kernel can crash a device when the Extended Echo feature (RFC 8335 ICMP probing) is co
Heap-based buffer overflow in Juniper Networks Junos OS on SRX Series devices that have Secure Vector Routing (SVR) enab
EUVD-2026-101447
GHSA-j54p-f459-hj35
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB