Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain control of configured BGP-LS peer
-
ExploitSend crafted BGP-LS Link NLRI advertisement
-
ExecutionTrigger reachable assertion in rpd
-
ImpactCrash routing daemon and disrupt routing (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V16 - Security Logging and Error Handling Reachable assertion handling
|
| Exploitation Conditions | Exploitation requires that the target Junos OS or Junos OS Evolved device be configured with BGP-LS and have an established BGP-LS peering session, and that the attacker occupy or control one of those configured BGP-LS peers (a pre-existing, operator-provisioned trust relationship) from which to send a crafted BGP-LS Link NLRI advertisement. Devices without BGP-LS configured are not affected. The principal limiting factor is this configured-peer prerequisite: although CVSS marks PR:N (no authentication in the protocol sense), the attacker cannot simply reach the service from anywhere - they must be positioned within an accepted BGP-LS adjacency. Impact is limited to a denial of service (rpd crash); no code execution, data disclosure, or integrity impact occurs. |
| Impact | This is a credible operational-risk denial-of-service issue rather than a code-execution or data-breach threat. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) rates it 8.7 (High) and reflects a network-reachable, low-complexity attack with no user interaction, with impact confined to availability (VA:H, plus SA:L on a subsequent system reflecting routing-plane disruption). There is no confidentiality or integrity impact (VC:N/VI:N). The headline PR:N is technically accurate but misleading on its own: the description explicitly limits exploitation to 'an attacker with access to a configured BGP-LS peer,' meaning the attacker must already occupy a trusted BGP-LS adjacency that the operator deliberately configured. That trust-relationship prerequisite substantially narrows the real attacker population versus a truly open internet-facing service. No EPSS score, CISA KEV entry, or public POC was provided in the input, so there is no signal of active or probable exploitation - exploitation status is 'no public exploit identified at time of analysis.' Net: real priority for Junos operators running BGP-LS (patch promptly), but not an indiscriminately exploitable, mass-scannable flaw; the configured-peer requirement and DoS-only impact temper the raw 8.7. |
| Exploit ScenarioDerived | An attacker who controls or has compromised a device configured as a BGP-LS peer of a Junos/Junos Evolved router sends a crafted BGP-LS Link NLRI advertisement. The malformed advertisement triggers a reachable assertion (CWE-617) in the routing protocol daemon (rpd), crashing it and disrupting routing on the target. No public exploit code was identified in the provided intelligence; exploitation requires an established BGP-LS peering relationship. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A crafted BGP-LS Link NLRI advertisement sent over an established BGP-LS peering session can trigger a reachable assertion inside the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved, causing rpd to crash and disrupting the device's routing control plane. Impact is limited to availability - no code execution, data disclosure, or integrity impact occurs - and only devices explicitly configured with BGP-LS and peered with the attacker's BGP-LS speaker are exposed, meaning the attacker must occupy or control one of the operator-provisioned BGP-LS peers. This is a credible operational-risk denial-of-service issue rather than a code-execution or data-breach threat; no public exploit code identified at time of analysis, and vendor patches are available per Juniper advisory JSA112187.
RemediationAI
Vendor-released patches: upgrade Junos OS to 26.2R1-S2, 25.4R1-S3, 25.2R2-S2, or 24.4R2-S5 or later, and Junos OS Evolved to 26.2R1-S2-EVO, 25.4R1-S3-EVO, 25.2R2-S2-EVO, 24.4R2-S5-EVO, 25.4X300-D40-EVO, or 25.2X100-D35-EVO as applicable; details and the per-release fix matrix are in Juniper advisory JSA112187 (https://supportportal.juniper.net/JSA112187). Because exploitation requires an existing BGP-LS peer, the most effective compensating controls are on the peering surface: if BGP-LS is not required in production, disable the BGP-LS address family and remove the peering configuration entirely (trade-off: loses the topology feed used by PCEs and SDN controllers), or, where BGP-LS must remain, restrict it to a minimal set of trusted, explicitly configured peer addresses and apply import policy/route filters that drop unexpected Link NLRI from those peers (trade-off: tight filters can silently suppress legitimate topology updates and require careful validation of the expected NLRI set). For devices that cannot be upgraded immediately, enable rpd core-dump collection and monitor for repeated rpd restarts or BGP-LS session flaps as an indicator of attempted exploitation. Note that no public exploit code was identified at time of analysis, so prioritization should be driven by exposure of BGP-LS peering rather than by observed in-the-wild activity.
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
BGP Link-State (BGP-LS, RFC 7752) is a BGP address-family extension used to export IGP/BGP topology - nodes, links, and prefixes encoded as NLRI - to external consumers such as path computation elements (PCEs) and SDN controllers. In this case the fault class is CWE-617 (Reachable Assertion): rpd reaches an internal consistency assertion while parsing or processing a crafted BGP-LS Link NLRI, and the daemon aborts rather than continuing. Because rpd is the control-plane process responsible for routing protocol adjacencies and route computation on Junos OS and Junos OS Evolved (both confirmed via the CPE strings cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved), a crash produces a denial of service that may also have limited subsequent-system availability effects (CVSS 4.0 vector rates SA:L). Juniper's CVSS 4.0 score is 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H); the independent assessment scores it as CVSS 3.1 8.7 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), which matches the same purely availability-focused impact. Notably, PR:N reflects the absence of protocol-level authentication, not unrestricted reachability: the crafted NLRI must be delivered inside an accepted, operator-provisioned BGP-LS adjacency, which is the principal limiting factor.
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-reachable, low-complexity crash with no user interaction; PR:N matches the vendor's peer-trust model, and impact is availability-only (A:H), with C:N/I:N.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker with access to a configured BGP-LS peer to cause an rpd crash via a crafted BGP-LS Link NLRI advertisements.
Executive ViewAI
Juniper Networks Junos OS and Junos OS Evolved devices configured for BGP-LS are exposed to a high-severity availability flaw that can crash the routing protocol daemon (rpd) when a malicious or compromised BGP-LS peer sends a crafted Link NLRI advertisement. The business risk is localized to routing control-plane disruption for organizations that have enabled BGP-LS and peer with an attacker-controlled BGP-LS speaker; there is no code execution, data disclosure, or integrity impact. Leadership should prioritize inventorying and patching those exposed Juniper routing devices because a successful trigger could cause network instability or outages in affected environments.
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-101347
GHSA-47rh-39cx-88pg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB