Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish or compromise BGP-LS peering session
-
ExploitSend crafted BGP-LS routing 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 device be configured for BGP-LS (BGP Link-State / RFC 7752 topology distribution) and that the attacker hold or hijack an established BGP peering session with the device - BGP-LS is not a default configuration and is typically deployed only where topology is exported to SDN controllers or path-computation elements. The description states the attacker is authenticated/network-based, implying a valid BGP adjacency rather than arbitrary unauthenticated internet access, which is the primary limiting factor; devices not running BGP-LS, or peering only with trusted and uncompromised neighbors, are not realistically exposed. Impact is confined to availability of the rpd routing process (denial of service) with automatic recovery, and no confidentiality or integrity impact applies. |
| Impact | This is a genuine but conditional priority. The CVSS 4.0 score of 8.7 (High) is driven entirely by availability impact (VA:H) against the routing daemon with a network attack vector and low attack complexity (AV:N/AC:L/AT:N). However, the real-world risk is substantially narrower than the raw score suggests. There is a direct CONFLICT in the data: the CVSS vector encodes PR:N (no privileges), yet the description explicitly states an 'authenticated network-based attacker' - for BGP-LS this almost certainly means the attacker must already have an established, configured BGP peering session with the target, which is a meaningful barrier not reflected in PR:N. No EPSS score, KEV listing, or POC is present in the input, so exploitation status is 'no public exploit identified at time of analysis' - this is not confirmed active exploitation and should not be treated as such. The CVSS 4.0 supplemental metrics reinforce caution rather than alarm: Automatable=Yes (AU:Y) and Recovery=Automatic (R:A), meaning a crash is self-recovering (rpd typically restarts), limiting durable impact to transient routing disruption. Net assessment: a credible availability threat for operators running BGP-LS with untrusted or compromisable peers, but not a drop-everything internet-wide emergency given the required peering relationship and absence of exploitation evidence. |
| Exploit ScenarioDerived | An attacker who controls or compromises a device with an established BGP-LS peering session to a target Junos/Junos OS Evolved router sends crafted BGP-LS (link-state) routing updates. The malformed update triggers a reachable assertion in the rpd (routing protocol daemon) process, crashing it and disrupting routing on the device until it recovers. No public proof-of-concept is identified in the available data; low attack complexity (AC:L) means no special timing or race conditions are required 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
Denial of service affecting the routing protocol daemon (rpd) in Juniper Networks Junos OS and Junos OS Evolved is triggered when crafted or malformed BGP-LS (BGP Link-State) routing updates hit a reachable assertion in the daemon, causing it to terminate. Per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the attacker must hold a valid, authenticated BGP peering session with the target and the device must be configured for BGP-LS; devices that do not run BGP-LS, or that peer only with trusted and uncompromised neighbors, are not realistically exposed. Impact is confined to availability of the rpd process with automatic recovery, no confidentiality or integrity impact applies, no public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
Patch available per vendor advisory: Juniper documents the fix in JSA112187 (https://supportportal.juniper.net/JSA112187), and the affected-version data identifies the corrected builds as Junos OS 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, and 26.2R1-S2, with the corresponding Evolved builds 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.4R1-S3-EVO, 25.2X100-D35-EVO, 25.4X300-D40-EVO, 26.2R1-S2-EVO, and 23.4X100 - upgrade to the corrected build for your train, since the version-specific suffix matters and a later-numbered maintenance release in a different train will not carry the fix. Because exploitation requires a BGP adjacency and BGP-LS, the most effective compensating control is to disable the BGP-LS address family (remove the family traffic-engineering/link-state configuration or the link-state export from the IGP) on any device that does not genuinely need topology export; the trade-off is that SDN controllers and PCEs lose their topology feed and path computation degrades. Where BGP-LS must remain enabled, harden the peering surface: enable MD5/TCP-AO authentication and GTSM/TTL-security on all BGP sessions so an off-path attacker cannot inject updates, restrict peers to a dedicated management-routing instance with ACLs on TCP/179, and rate-limit BGP-LS update processing; these reduce but do not eliminate the exposure from a compromised but legitimately authenticated neighbor. As a last resort, monitor and auto-restart rpd or fail over to a redundant routing engine, but note that this only shortens the outage window and does not prevent the crash.
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 Junos's rpd routing protocol daemon, the process responsible for BGP and related routing protocol operation. BGP-LS (BGP Link-State, RFC 7752) is an address-family extension that carries IGP topology (nodes, links, prefixes) over BGP, typically so an SDN controller or path-computation element can build a topology view; it is not enabled by default and requires explicit configuration. The root cause is CWE-617 (Reachable Assertion): a reachable assert/abort path in rpd is hit while processing BGP-LS update content, so the daemon aborts rather than handling the input gracefully. The CPE data identifies two distinct code bases, juniper_networks:junos_os and juniper_networks:junos_os_evolved, meaning fixes must be applied independently to each train. The vulnerability is a pure availability fault against the control plane - no memory corruption, data disclosure, or configuration modification is described - and the assertion aborts only the affected daemon, which Junos restarts, so recovery is expected but routing sessions reconverge during the interruption.
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
Exploitation needs an established authenticated BGP-LS peering session so PR:L (not PR:N); network vector and low complexity hold, and impact is availability-only on the local rpd (C:N/I:N/A:H, S:U).
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 an authenticated network-based attacker to cause a denial of service via BGP-LS routing updates.
Executive ViewAI
A denial-of-service vulnerability in Juniper Networks Junos OS and Junos OS Evolved can cause the routing protocol daemon (rpd) to terminate when processing crafted BGP-LS updates, potentially disrupting network routing. Exploitation requires an authenticated BGP peering session and BGP-LS configuration, limiting exposure to specific network environments; no public exploit identified at time of analysis. While the daemon recovers automatically, repeated attacks could impact network stability, making timely patching important for organizations running these configurations.
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-101345
GHSA-xfj9-8jjx-xv95
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB