Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLeverage established EVPN BGP peering
-
ExploitSend crafted EVPN BGP route updates
-
ExecutionTrigger integer overflow in rpd
-
ImpactCrash rpd, disrupt control-plane adjacencies
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 target to run an EVPN-enabled routing instance on Junos OS or Junos OS Evolved AND an already-established EVPN BGP peering relationship between the attacker-controlled endpoint and the victim's rpd - the attacker must therefore be a configured/trusted BGP neighbor or have compromised one, not an arbitrary internet host. The specific trigger is malformed EVPN BGP route processing that causes an integer overflow (CWE-190). Limiting factors: EVPN is a non-default, deliberately configured feature; the peering trust relationship must pre-exist; impact is availability-only (control-plane DoS) with no confidentiality or integrity effect. These constraints meaningfully narrow realistic exploitation to EVPN deployments and adjacent/compromised peers despite the network attack vector. |
| Impact | The vendor-supplied CVSS 4.0 base score of 8.7 (AV:N/AC:L/PR:N/UI:N) with VA:H and subsequent-system SA:L reflects a high-severity, network-reachable denial of service against the rpd routing process, and the supplemental metrics reinforce priority (AU:Y automatable, R:A recovery requires action). However, these raw metrics materially overstate exposure: the description explicitly requires 'an established EVPN BGP peering relationship,' meaning only a configured, trusted BGP neighbor (or an attacker who has compromised/spoofed such a peer) can deliver the malicious route updates - this is a significant gating condition that PR:N does not capture. No EPSS probability was provided, there is no CISA KEV listing, and no proof-of-concept is referenced, so this is 'no public exploit identified at time of analysis.' Net assessment: a genuine priority for operators running EVPN fabrics (service providers, data-center overlays) because the impact is control-plane outage and the trigger is automatable once peering exists, but NOT a broadly internet-exploitable mass-threat given the trust-relationship prerequisite. Missing data to note: no affected-version list beyond wildcard CPEs, and no EPSS/KEV signals to corroborate real-world exploitation likelihood. |
| Exploit ScenarioDerived | An attacker controlling or having compromised a device that holds an established EVPN BGP peering session with a target Junos OS / Junos OS Evolved router sends crafted EVPN BGP route updates. Processing these in rpd triggers an integer overflow that crashes the routing process, dropping control-plane adjacencies and causing a denial of service across the EVPN-enabled routing instance. No public exploit code is identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Denial of service in Juniper Networks Junos OS and Junos OS Evolved allows a remote attacker who already holds an established EVPN BGP peering relationship with a target device to disrupt the routing protocol daemon (rpd) by sending EVPN BGP routes that trigger an integer overflow or wraparound. The flaw affects EVPN-enabled routing instances and can tear down control-plane adjacencies and halt route processing, producing an availability-only impact with no confidentiality or integrity effect. EVPN is a deliberately configured, non-default feature and the peering trust relationship must pre-exist, so realistic exploitation is limited to EVPN deployments and adjacent or compromised BGP peers; no public exploit code was identified at time of analysis, and the vendor advisory is Juniper JSA112187.
RemediationAI
Treat Juniper advisory JSA112187 (https://supportportal.juniper.net/JSA112187) as the authoritative source for the affected release matrix and for the exact Junos OS and Junos OS Evolved versions containing the fix, and upgrade to those vendor-designated releases; no fixed version number is asserted here because the provided intelligence does not include one, and no vendor workaround was supplied with this data. Until the upgrade can be scheduled, reduce exposure by keeping EVPN enabled only on routing instances that genuinely require it, since disabling EVPN removes the vulnerable code path entirely but breaks EVPN/VXLAN or EVPN-MPLS service and must be coordinated with the fabric design. Harden the trust boundary that the flaw depends on: enforce TCP-MD5 or TCP-AO authentication and strict BGP peer authentication on EVPN sessions, and restrict EVPN peering to known neighbor addresses via firewall filters on port 179 and prefix limits; note these controls only prevent unauthorized peers from establishing sessions and do not sanitize malformed routes from a legitimate or compromised peer. Additionally, apply inbound routing policy on EVPN sessions to constrain which route types and communities are accepted and to cap the number of accepted EVPN NLRI, accepting the trade-off that overly tight filters can drop legitimate EVPN routes and cause reachability gaps. Because the issue is availability-only in rpd, routing-engine-level protections such as graceful restart or BGP session damping can shorten the outage window but do not prevent the initial daemon fault.
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 an integer overflow or wraparound (CWE-190) in the rpd routing protocol daemon, the Junos process responsible for BGP and other routing protocol adjacencies. It is reached through EVPN (Ethernet VPN, RFC 7432-style BGP MPLS/IP EVPN) route processing: when a peer advertises crafted EVPN NLRI/route attributes, a length, count, or offset value used during parsing or route installation wraps, leading to a fault that terminates or wedges the daemon and its control-plane sessions. Because rpd handles all routing adjacencies on the device, a crash or stall degrades control-plane convergence broadly, but the impact remains availability-only. CPE data identifies both cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved as affected product families; the CPE entries are wildcarded so no precise version boundary is asserted in this data set, and the authoritative version matrix must be taken from Juniper's JSA112187 advisory. Network reachability is high (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N) and the supplemental metrics flag automatable exploitation (AU:Y) and remediation requiring operator action (R:A), while an independent CVSS 3.1 assessment of AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H aligns on a high-severity availability-only outcome. Despite the PR:N ratings, practical exploitation requires the victim to run an EVPN-enabled routing instance and a pre-established EVPN BGP peering relationship, meaning the attacker must be a configured/trusted neighbor or have compromised one rather than an arbitrary internet host.
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
Network-triggered via BGP updates (AV:N/AC:L); PR:N since BGP peering is a trust relationship not device privileges; availability-only DoS, and S:C because the rpd crash disrupts neighbors' control-plane adjacencies beyond the vulnerable process.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
An Integer Overflow or Wraparound vulnerability in the rpd process of Juniper Networks Junos OS and Junos OS Evolved allows a remote attacker with an established EVPN BGP peering relationship to cause a denial of service via EVPN BGP route processing. The issue affects EVPN-enabled routing instances and can disrupt control-plane adjacencies.
Executive ViewAI
Juniper Networks Junos OS and Junos OS Evolved contain a high-severity vulnerability that can cause the routing protocol daemon to crash, disrupting network routing in EVPN-enabled environments. Organizations with EVPN deployments and established BGP peering relationships face potential network outages, impacting service availability and business continuity. No public exploit identified at time of analysis, but with no vendor patch currently available, leadership should prioritize identifying affected systems and implementing interim mitigations.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict EVPN BGP peering to trusted peers, apply route filters, disable EVPN where not required, monitor rpd for crashes, and follow Juniper JSA112187 for updates.
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-101323
GHSA-rprv-3hqm-hw97
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB