Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish or abuse authenticated BGP peering session
-
ExploitSend crafted BGP route updates
-
ExecutionTrigger integer overflow in rpd
-
ImpactCrash routing daemon and disrupt routing (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the extended-nexthop-tunnel feature to be explicitly enabled (a non-default configuration) on the target Junos OS / Junos OS Evolved device, AND the attacker must be an established BGP peer - the description specifies an 'authenticated BGP peer,' meaning a configured BGP neighbor relationship with the target rpd is a prerequisite. Once those conditions hold, the attacker sends crafted BGP route updates that trigger the integer overflow. Limiting factors: devices without extended-nexthop-tunnel enabled are not affected, and the attacker must already occupy or compromise a trusted BGP peering position, which significantly narrows the realistic attack surface despite the network attack vector. Note the vendor vector lists PR:N, which conflicts with the described authenticated-peer requirement. |
| Impact | The vendor CVSS 4.0 base score of 8.7 (High) is driven almost entirely by a high availability impact on the vulnerable system (VA:H) plus a low subsequent-system availability impact (SA:L), with no confidentiality or integrity exposure - consistent with a routing-daemon crash rather than code execution or data theft. No EPSS probability, CISA KEV entry, or public POC was supplied, so there is no evidence of active or imminent widespread exploitation; exploitation status is best characterized as no public exploit identified at time of analysis. A key conflict must be flagged: the vendor CVSS vector states PR:N (no privileges) while the description explicitly requires an 'authenticated BGP peer,' which implies the attacker must already hold an established, configured BGP peering relationship with the target - verify the true privilege requirement with Juniper, as this materially changes the attacker-prerequisite picture. Exploitation is further gated by the non-default extended-nexthop-tunnel feature being enabled. Net assessment: this is a credible operational-availability risk for carriers and enterprises running BGP with that feature, but it is not a drive-by, fully-unauthenticated internet-wide threat - realistic risk is bounded to environments with the feature enabled and reachable/compromised BGP neighbors, making it a targeted rather than mass-exploitation concern pending exploitation data. |
| Exploit ScenarioDerived | An attacker who controls or has compromised a configured BGP peer of a Junos OS or Junos OS Evolved device with extended-nexthop-tunnel enabled sends specially crafted BGP route updates. These updates trigger an integer overflow (CWE-190) in the routing daemon (rpd), crashing it and causing a denial of service that disrupts routing on the affected device. No public exploit code has been identified; given AV:N/AC:L the update itself is simple to send once a peering session exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Crafted BGP route updates sent by an established BGP peer can trigger an integer overflow in the rpd routing daemon of Juniper Networks Junos OS and Junos OS Evolved, crashing the process and causing a denial of service. The flaw is only reachable when the non-default extended-nexthop-tunnel feature is explicitly enabled on the target device, and the attacker must already hold a configured BGP peering relationship with the device, meaning a trusted routing position is a prerequisite rather than anonymous internet exposure. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor CVSS 4.0 score of 8.7 reflects high availability impact on the local system with no confidentiality or integrity exposure; note that the vendor vector lists PR:N while the vendor's own description and our assessment specify an authenticated BGP peer, a conflict that should be resolved using the description's authentication requirement.
RemediationAI
No fixed release version is specified in the available input data, so the authoritative remediation source is the vendor advisory JSA112187 (https://supportportal.juniper.net/JSA112187), which lists the patched Junos OS and Junos OS Evolved releases; upgrade to the corresponding fixed train as soon as the advisory-specific version for your platform is confirmed, and treat any absence of a version number here as an advisory-reference gap rather than a statement that no fix exists. If an immediate upgrade is not possible, the most effective compensating control is to remove the extended-nexthop-tunnel configuration on affected devices, which eliminates the vulnerable code path entirely; the trade-off is loss of next-hop tunneling functionality used in certain IPv4-over-IPv6 or MPLS-adjacent designs, so this must be validated against the routing architecture before removal. A second layer is to restrict BGP peering to a tightly bounded set of trusted, authenticated neighbors and to apply route-update rate limiting (such as damping or per-peer update throttling) plus maximum-prefix limits, which reduces the likelihood that a single peer can deliver the malformed update volume needed to trigger the overflow; these controls add operational complexity and can cause legitimate route churn to be suppressed if tuned too aggressively. Because exploitation requires a pre-existing BGP session, monitoring BGP session resets and rpd restarts on devices with extended-nexthop-tunnel enabled can provide early warning of attempts to weaponize this flaw.
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 a CWE-190 Integer Overflow or Wraparound in Juniper's rpd (routing protocol daemon), the process that implements BGP and other routing protocols on Junos OS and Junos OS Evolved. It is reachable through BGP route update processing when the extended-nexthop-tunnel capability is configured, a feature that allows next-hop information of a different address family to be carried in BGP announcements (IPv4 NLRI with an IPv6 next hop, or similar encapsulation scenarios) so that routes can be resolved over a tunnel. When rpd parses or performs arithmetic on values derived from those extended next-hop attributes, an integer overflow/wraparound occurs, which corrupts internal state and terminates the routing process. Because rpd handles route computation for the control plane, a crash can disrupt routing and forwarding for the affected device rather than just blocking a single session. The CPE data lists both juniper_networks:junos_os and juniper_networks:junos_os_evolved, confirming that the mainstream Junos OS train and the Evolved (Linux-based) train share the vulnerable code path; the CPE entries use wildcard versions, so exact affected releases are only enumerated in the vendor advisory JSA112187. No confidentiality or integrity impact is expected, since the failure mode is a control-plane crash rather than memory corruption exploitable for code execution.
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/AU:Y/R:A/V:C/RE:M
An established/authenticated BGP peer is required so PR:L (not PR:N); crafting the update is simple so AC:L; only rpd availability is affected (A:H), with no confidentiality or integrity impact.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
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.
Executive ViewAI
Juniper Networks' Junos OS and Junos OS Evolved routing platforms can lose their routing process - and with it network reachability for the traffic those devices carry - when an already-established BGP peer sends a crafted route update. Exposure is limited to devices where the non-default extended-nexthop-tunnel feature has been enabled, and a trusted peering relationship is a prerequisite, so risk is concentrated in core and edge routing roles rather than internet-facing services. No public exploit code or confirmed active exploitation has been identified at time of analysis, and no vendor-released patch exists yet, so leadership should expect a configuration, monitoring, and peering-trust response in the near term rather than a straightforward upgrade.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the non-default extended-nexthop-tunnel feature wherever not operationally required; restrict BGP peering to explicitly trusted peers and enforce TCP MD5 or TCP-AO authentication with maximum-prefix and route-filter limits; apply inbound BGP update rate limiting; monitor and alert on rpd process restarts and session flaps; maintain redundant routing paths, graceful restart, and out-of-band management; track the Juniper SIRT advisory for an upcoming hotfix or vendor workaround.
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
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
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-101349
GHSA-5x3h-q26c-2282
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB