Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network position to device
-
ExploitCraft malformed MPLS LSP-ping packet
-
ExecutionSend to rpd and trigger faulty reference handling
-
ImpactCrash routing daemon (control-plane DoS)
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires an adjacent-network (AV:A) position - the attacker must be on the same L2 broadcast domain or a directly connected link to the target - and the device must be processing MPLS LSP-ping (MPLS OAM echo-request) traffic reaching the rpd, implying MPLS is deployed and enabled. No authentication (PR:N) and no user interaction (UI:N) are needed, and default-configuration devices running MPLS are affected across the listed Junos OS and Junos OS Evolved trains. The primary limiting factor is the adjacency requirement: the flaw is not remotely reachable across routed/Internet paths, so blast radius is confined to attackers with local network reach, and impact is limited to availability (routing daemon crash) with no data exposure or modification. |
| Impact | This is a moderate-priority availability vulnerability, not a critical compromise. The supplied CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L, base 7.1) is internally consistent with the description: an unauthenticated attacker with an adjacent-network position can crash the routing protocol daemon (rpd), yielding a denial of service with no confidentiality or integrity impact. The low attack complexity and lack of required privileges or user interaction make exploitation technically easy FOR an attacker who already holds adjacent access, but the AV:A constraint - not AV:N - is the dominant limiting factor and sharply narrows the realistic threat population to attackers on the same L2 segment or a directly connected link. No EPSS score, SSVC decision, KEV listing, or POC indicator was provided in the input, so exploitation likelihood cannot be quantified; there is no public exploit identified at time of analysis and no evidence of active exploitation. SA:L signals a minor spillover effect on connected systems (e.g., routing adjacencies dropping), consistent with an rpd crash propagating control-plane disruption. Net: a legitimate patch-worthy DoS against routing infrastructure, but weighted well below network-reachable RCE-class issues. |
| Exploit ScenarioDerived | An attacker positioned on an adjacent network segment or directly connected link to a vulnerable Junos OS / Junos OS Evolved device sends a specifically malformed MPLS LSP-ping (echo request) packet to the target. The rpd daemon mishandles the packet (CWE-688, function call with an incorrect variable/reference argument) and crashes, disrupting routing and causing a denial of service. No public exploit code was identified at time of analysis, and no authentication or user interaction is required. |
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 Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to crash the routing protocol daemon (rpd) by sending specifically malformed LSP-ping packets; this is a moderate-priority availability vulnerability, not a critical compromise, because it requires an adjacent-network position and MPLS LSP-ping processing to be enabled. No public exploit has been identified at time of analysis, and Juniper has released fixed software versions for both Junos OS and Junos OS Evolved. Successful exploitation causes only availability impact to rpd, with no data exposure or modification.
RemediationAI
Vendor-released patch: upgrade Junos OS to 23.2R2-S7.7 or later, 23.4R2-S8.13 or later, 24.2R2-S5.5 or later, 24.4R2-S5 or later, 25.2R2-S2 or later, 25.4R1-S3 or later, or 26.2R1-S2 or later; upgrade Junos OS Evolved to 23.2R2-S7.7-EVO or later, 23.4R2-S8.11-EVO or later, 24.2R2-S5.6-EVO or later, 24.4R2-S5-EVO or later, 25.2R2-S2-EVO or later, 25.2X100-D35-EVO or later, 25.4R1-S3-EVO or later, 25.4X300-D40-EVO or later, or 26.2R1-S2-EVO or later. For Junos OS Evolved 23.4X100, the provided data lists it as affected but does not state a separate fixed version, so consult JSA112187 at https://supportportal.juniper.net/JSA112187 for the applicable replacement. If immediate upgrade is not possible, reduce exposure by filtering or blocking MPLS OAM/LSP-ping traffic from untrusted adjacent interfaces using Junos firewall filters, and restrict L2 adjacency to trusted network segments; the trade-off is that legitimate LSP-ping monitoring may be disrupted. If LSP-ping/MPLS OAM is not operationally required, disabling it where supported removes the attack surface but sacrifices MPLS fault detection and troubleshooting; monitor for rpd crashes as a detection signal. Patch is available from the vendor, and no public exploit has been identified at time of analysis.
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 routing protocol daemon in Juniper Networks Junos OS and Junos OS Evolved, and the root-cause class is CWE-688 (Function Call With Incorrect Variable or Reference as Argument), meaning malformed input can cause a function to be invoked with an incorrect variable or reference and ultimately crash the daemon. LSP-ping is an MPLS Operations, Administration, and Maintenance (OAM) echo protocol used to verify label-switched-path connectivity; the flaw is triggered when rpd processes specifically malformed LSP-ping traffic. The CPEs cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:* and cpe:2.3:a:juniper_networks:junos_os_evolved:*:*:*:*:*:*:*:* identify the affected product families. The CVSS 4.0 vector is AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L, and the independent assessment is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so exploitation requires an adjacent-network position on the same L2 broadcast domain or a directly connected link, no authentication, and no user interaction; the device must be processing MPLS LSP-ping traffic reaching rpd, implying MPLS is deployed and enabled. The flaw is not remotely reachable across routed or Internet paths, and impact is limited to availability, with no confidentiality or integrity loss.
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 unauthenticated packet crashes rpd with no interaction, so AV:A/AC:L/PR:N/UI:N; impact is availability-only (A:H, C:N/I:N) within the same component (S:U).
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
4DescriptionCVE.org
A Function Call With Incorrect Variable or Reference as Argument vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to cause an rpd crash via specifically malformed LSP-ping.
Executive ViewAI
Juniper Junos OS and Junos OS Evolved contain a high-severity denial-of-service vulnerability that can allow an attacker on an adjacent network to crash the routing protocol daemon (rpd), potentially causing network routing disruptions and availability loss. Organizations using affected Juniper devices with MPLS LSP-ping enabled are at risk of operational downtime, though no public exploit identified at time of analysis. Leadership should prioritize patching to maintain network resilience and avoid service interruptions.
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-101311
GHSA-vqw7-gfmm-3mrr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB