Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish/compromise adjacent eBGP peer
-
ExploitSend crafted VPLS signaling update
-
ExecutionTrigger reachable assertion in rpd
-
ImpactRouting daemon crash and denial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V16 - Security Logging and Error Handling Reachable assertion handling
|
| Exploitation Conditions | Exploitation requires that the target run VPLS with 'automatic site-ID negotiation' enabled - this specific feature is the triggering precondition named in the description, and without it the vulnerable code path is not reachable. The attacker must additionally be an adjacent eBGP peer (AV:A), meaning an established external BGP peering session with the victim router is required, limiting exploitation to directly peered neighbors rather than arbitrary remote hosts. Limiting factors: non-default VPLS auto site-ID negotiation configuration, the need for an existing eBGP adjacency, and impact confined to availability (rpd crash/DoS) with no data exposure or code execution. |
| Impact | This is a moderate-priority availability issue, not a drop-everything emergency. The CVSS 4.0 base score of 7.1 is driven entirely by availability impact (VA:H, SA:L) with no confidentiality or integrity effect, and critically the attack vector is Adjacent (AV:A), not Network - the attacker must be a directly configured eBGP peer, which sharply limits the attacker population to entities already in a BGP peering relationship. No EPSS score, KEV listing, or POC was provided in the intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Although the Juniper CVSS vector uses PR:N (no system privileges required), real-world exploitation requires an established eBGP adjacency, which is itself a configuration/trust relationship - this is a meaningful mitigating factor the raw PR:N metric understates. SSVC-style framing: exploitation is not observed, technical impact is partial (daemon crash/DoS of rpd, not total system compromise), and automatability is low because the attacker needs peering adjacency plus a non-default feature. Net: a legitimate patch-management priority for operators running VPLS with automatic site-ID negotiation, but low real-world risk for the broad Junos install base that does not enable that feature. |
| Exploit ScenarioDerived | An attacker who controls (or has compromised) a device configured as an adjacent eBGP peer of a vulnerable Junos OS / Junos OS Evolved router sends a crafted VPLS signaling update. When automatic site-ID negotiation is enabled, the update triggers a reachable assertion in the routing protocol daemon (rpd), crashing the daemon and causing a denial of service. No public exploit code was identified at time of analysis; exploitation requires an existing eBGP peering relationship and the non-default negotiation feature. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Oct 14, 2026
An adjacent eBGP peer can crash the Juniper Junos OS and Junos OS Evolved routing protocol daemon (rpd) by sending a crafted VPLS signaling update, but only on routers where VPLS automatic site-ID negotiation is enabled and an external BGP peering session is already established. The flaw is a reachable assertion (CWE-617) in rpd that terminates the process, producing a denial of service with no confidentiality or integrity impact; Juniper rates it 7.1 under CVSS 4.0, and our independent assessment scores it CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, treating it as a moderate-priority availability issue rather than an emergency. No public exploit code has been identified at time of analysis, and the vulnerability is not confirmed actively exploited (no CISA KEV listing), so risk is concentrated in networks that combine external BGP peering with non-default VPLS auto site-ID negotiation.
Earlier versions of this analysis (2)
Denial of service in Juniper Networks Junos OS and Junos OS Evolved occurs when an adjacent eBGP peer sends a crafted VPLS signaling update while automatic site-ID negotiation is enabled, triggering a reachable assertion (CWE-617) that crashes the routing protocol daemon (rpd). The vendor assigns CVSS 7.1 (CVSS 4.0) with adjacent network access and no authentication or user interaction required, but exploitation is conditional: the attacker must already have an established eBGP peering relationship with the target and the VPLS automatic site-ID negotiation feature must be configured. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the independent assessment characterizes this as a genuine but conditional availability risk rather than a pervasive emergency.
A reachable assertion in the routing protocol daemon (rpd) of Juniper Junos OS and Junos OS Evolved can be triggered by an adjacent eBGP peer, causing a denial of service. The vulnerability requires that VPLS with automatic site-ID negotiation be enabled on the target device. No authentication or user interaction is needed (CVSS PR:N/UI:N), but the attacker must be a configured adjacent eBGP peer. No public exploit code has been identified at time of analysis, and the issue is rated medium severity (CVSS 6.5) with availability-only impact.
RemediationAI
No exact fixed version is provided in the available input data, so the authoritative source for the patch matrix is Juniper's advisory JSA112187 (https://supportportal.juniper.net/JSA112187); consult it and upgrade Junos OS or Junos OS Evolved to the recommended release for your platform and train (Patch availability is confirmed per vendor advisory, but the specific fixed version is not independently verifiable from the supplied data). Until an upgrade can be scheduled, the most direct compensating control is to disable VPLS automatic site-ID negotiation and use manually configured, unique site IDs per provider-edge router, which removes the precondition that makes the assertion reachable; the trade-off is operational overhead and the need to keep site-ID assignments consistent across the VPLS domain during any migration, which can cause signaling or forwarding disruption if done inconsistently. Because the attacker must already be an adjacent eBGP peer, reducing the population of routers that can reach rpd's signaling path is also effective: restrict eBGP sessions to explicitly trusted neighbors, apply GTSM/TTL-security and TCP MD5 or TCP-AO authentication on those sessions to prevent session hijacking or spoofed adjacency, and enable BGP prefix and route limits - though these controls reduce exposure rather than eliminate the assertion itself and do add configuration and troubleshooting complexity. Monitor for rpd crashes and unexpected daemon restarts on VPLS routers as an indicator that the vulnerable path is being exercised.
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 affected component is rpd, the Juniper routing protocol daemon that handles BGP, MPLS/VPLS signaling, and related control-plane functions on Junos OS and Junos OS Evolved (CPE entries cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved, both with wildcarded versions in the supplied data). VPLS uses BGP as a discovery and signaling mechanism, auto-discovering provider-edge peers and, when automatic site-ID negotiation is configured, deriving site identifiers from signaling messages rather than from static per-router configuration. The root cause is CWE-617 (Reachable Assertion): a signaling update that reaches the auto site-ID negotiation path violates an internal invariant, triggering an assertion failure inside rpd instead of being handled gracefully. Because the daemon aborts, the router loses its routing and signaling state until rpd restarts, which is an availability-only impact. The attack surface is bounded by two conditions explicit in the description and confirmed by our assessment: the router must be running VPLS with automatic site-ID negotiation enabled, and the attacker must be an adjacent eBGP peer, i.e., a directly peered external BGP neighbor (AV:A). This means exploitation is not reachable by arbitrary internet hosts, only by an established eBGP peer whose session reaches the vulnerable signaling code path.
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:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
Adjacent eBGP peer so AV:A; no system privileges per vendor so PR:N; single crafted update needs no special conditions (AC:L); impact is rpd DoS only, so A:H with C:N/I:N.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
4DescriptionCVE.org
A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent eBGP peer to cause a denial of service via a VPLS signaling update when automatic site-ID negotiation is enabled.
Executive ViewAI
Juniper Junos OS and Junos OS Evolved routers configured with both external BGP peering and VPLS automatic site-ID negotiation are exposed to a denial-of-service condition that can crash the routing protocol daemon and disrupt network availability. Leadership should care because this targets core routing infrastructure, but risk is limited to networks meeting those specific configuration requirements, and no public exploit identified at time of analysis. With no vendor-released patch identified at time of analysis, near-term risk management depends on configuration controls and monitoring.
No vendor-released patch identified at time of analysis. Interim mitigations: disable VPLS automatic site-ID negotiation where not required; restrict external BGP peering to trusted adjacent peers; monitor rpd process stability and BGP/VPLS signaling logs for crash or restart events; apply Juniper-published workarounds if available.
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-101478
GHSA-7f8h-597j-f5xc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB