Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish or compromise configured BGP-LS peer
-
ExploitSend crafted BGP-LS update
-
ExecutionTrigger reachable assertion in rpd
-
ImpactCrash routing daemon, 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 BGP-LS (BGP Link-State) and have an established, operator-configured BGP-LS peering session; the attacker must act as a configured BGP-LS peer and send a malicious BGP-LS update that reaches the rpd process. Limiting factors: devices without BGP-LS configured are not exposed, and the attacker must occupy or spoof an already-trusted, configured peer relationship (BGP sessions are typically point-to-point with known neighbors), which narrows the viable attacker set. Impact is confined to denial of service of the routing process; no confidentiality or integrity impact applies. |
| Impact | This is a credible operational-availability risk for networks that run BGP-LS, but not a 'drop everything' internet-facing emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) scores 8.7 (High) and reflects a network-reachable, low-complexity trigger with high availability impact (VA:H) plus a lesser subsequent-system availability effect (SA:L). However, the description materially constrains the raw vector: the attacker must be 'a configured BGP-LS peer,' meaning exploitation requires an already-established, operator-configured BGP-LS peering relationship rather than arbitrary unauthenticated internet access. That gap between PR:N and the real-world 'configured peer' prerequisite should be noted - the flaw is remotely triggerable in protocol terms but gated by the trust/configuration boundary of BGP peering. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or available exploit code. CWE-617 (Reachable Assertion) is consistent with a deterministic crash/restart of the rpd routing daemon rather than code execution or data compromise (VC:N/VI:N). Net: a real priority for BGP-LS-enabled service-provider and large-enterprise edge/core routers because rpd disruption degrades routing, but lower urgency where BGP-LS is not configured or peers are tightly controlled and trusted. |
| Exploit ScenarioDerived | An attacker who controls, spoofs, or compromises a device that is a configured BGP-LS peer of a vulnerable Junos/Junos OS Evolved router sends a specially crafted BGP-LS update. The update drives the rpd process into a reachable assertion failure, crashing or restarting the routing daemon and disrupting routing on the target. No public exploit code is identified at time of analysis, and the attack requires an established BGP-LS peering relationship rather than arbitrary network access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
The Juniper Junos OS routing process (rpd) can be crashed by a configured BGP-LS peer sending a specially crafted BGP-LS update, resulting in a denial of service. This reachable assertion vulnerability (CWE-617) affects Junos OS and Junos OS Evolved only when BGP-LS is configured and a peering session is established, requiring the attacker to be an already-trusted, configured BGP-LS peer. No public exploit code or active exploitation has been identified at the time of analysis, but the CVSS score of 8.7 reflects the high availability impact.
RemediationAI
Consult Juniper advisory JSA112187 (https://supportportal.juniper.net/JSA112187) for patch availability and exact fixed version details; no specific fix version was provided in the available data. As a primary action, apply the vendor-recommended update once available. If BGP-LS is not operationally required, disable it by removing the bgp-ls configuration or deactivating the link-state address family to eliminate exposure entirely. If BGP-LS must remain enabled, restrict BGP-LS peering to trusted, statically configured peers using BGP authentication (e.g., MD5) and inbound ACLs on the routing engine interface, and monitor rpd for unexpected restarts. These mitigations trade off reduced BGP-LS functionality or increased management overhead. Given the requirement for a configured peer, this is a credible operational-availability risk for networks running BGP-LS, but not an internet-facing emergency; prioritize patching accordingly.
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 resides in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved. rpd is responsible for maintaining routing tables and processing routing protocol messages, including BGP-LS (BGP Link-State), an address family used to distribute network topology information (nodes, links, prefixes) to external controllers for path computation or SDN applications. The CWE-617 (Reachable Assertion) flaw means that a specific sequence or content in a BGP-LS update triggers an assertion in the code, causing rpd to abort and restart, which disrupts routing. The attack vector is network-based (AV:N) with no privileges required (PR:N) and no user interaction (UI:N), but exploitation requires that the target device has BGP-LS configured and an established BGP-LS peering session with the attacker, meaning the attacker must already be a trusted BGP-LS peer. The impact is limited to availability (VA:H); confidentiality and integrity are unaffected. The CPE entries (cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:* and cpe:2.3:a:juniper_networks:junos_os_evolved:*:*:*:*:*:*:*:*) indicate that all versions are potentially affected unless patched.
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 a crafted BGP-LS update from a configured peer with low complexity and no UI; DoS-only, so C:N/I:N/A:H; PR:N kept to mirror vendor despite the configured-peer precondition.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
A Reachable Assertion vulnerability in the rpd process of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP-LS peer to cause a denial of service via a BGP-LS update.
Executive ViewAI
Juniper Junos OS and Junos OS Evolved environments with BGP-LS configured face a denial-of-service risk that can crash the routing process (rpd) when a trusted BGP-LS peer sends a crafted update. The exposure is limited to organizations that have established BGP-LS peering sessions, meaning a malicious or compromised peer could disrupt network availability; no public exploit identified at time of analysis. Leadership should care because an unpatched device could suffer routing instability until the vendor patch is applied.
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-101368
GHSA-jq56-4qrc-gvfq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB