Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish/control configured BGP peer session
-
ExploitSend crafted BGP UPDATE message
-
ExecutionTrigger NULL pointer dereference in rpd
-
ImpactCrash routing daemon (DoS)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the target Junos OS / Junos OS Evolved device to have BOTH ISO-VPN and egress-protection configured and enabled - a non-default feature combination - and the attacker must be an already-configured BGP peer of the device sending a malicious BGP UPDATE. Although CVSS marks PR:N (no authentication, consistent with BGP's lack of session authentication), the requirement for a pre-established, operator-configured peering relationship is the key limiting factor: arbitrary Internet hosts cannot reach the vulnerable code path. Devices without ISO-VPN egress protection, or without the attacker as a configured peer, are not exploitable. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) scores 8.7 (High), driven entirely by availability impact - a NULL pointer dereference crashing the rpd routing daemon (denial of service), with no confidentiality or integrity impact (VC:N/VI:N). The network attack vector and PR:N nominally indicate unauthenticated remote exploitation, but the description scopes the attacker to a 'configured BGP peer,' meaning exploitation requires an established, operator-configured BGP peering session rather than arbitrary Internet reachability - this materially narrows the real-world attack surface versus what AV:N/PR:N alone implies. Exploitation is further gated by a non-default precondition: both ISO-VPN and egress-protection must be configured and enabled. No EPSS score, SSVC decision data, KEV listing, or POC is present in the provided intelligence, so there is no public-exploitation signal: this is a vendor-reported (Juniper) issue with no public exploit identified at time of analysis. Net assessment: a genuine high-availability-impact DoS for the specific population of Junos/Junos OS Evolved devices running ISO-VPN egress protection with BGP peers, but not a broadly exploitable 'anyone on the network' flaw - real priority is conditional on that configuration, not universal. |
| Exploit ScenarioDerived | An attacker who controls or has compromised a device that is an already-configured BGP peer of a vulnerable Junos OS / Junos OS Evolved router (with ISO-VPN and egress-protection enabled) sends a crafted BGP UPDATE message. Processing the UPDATE triggers a NULL pointer dereference in the rpd routing daemon, crashing it and causing a denial of service. No public exploit code is identified at time of analysis; exploitation requires an existing BGP 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
A NULL pointer dereference in the rpd routing daemon of Juniper Networks Junos OS and Junos OS Evolved lets an unauthenticated, already-configured BGP peer crash the routing process by sending a crafted BGP UPDATE, producing a denial of service, but only on devices where both ISO-VPN and egress-protection are enabled - a non-default feature combination. The CVSS 4.0 vector scores 8.7 (High) and is driven entirely by availability impact (VC:N/VI:N/VA:H/SC:N/SI:N/SA:L), with no confidentiality or integrity loss. No public exploit code and no confirmed active exploitation were identified at time of analysis; arbitrary Internet hosts cannot reach the vulnerable code path because the sender must already be an operator-configured BGP peer of the target device.
RemediationAI
Juniper has published the security advisory JSA112187 (https://supportportal.juniper.net/JSA112187); consult it for the exact fixed Junos OS and Junos OS Evolved service releases and upgrade to the recommended build for your platform, since no independent patch version was confirmed in the source data. If immediate upgrade is not possible, the most direct mitigation is to disable either ISO-VPN egress protection or the ISO-VPN address family where that functionality is not operationally required - this removes the vulnerable code path entirely at the cost of losing egress-link backup protection or VPN reachability. Because only an already-configured BGP peer can trigger the crash, tighten BGP peering to trusted neighbors only, enable BGP session authentication (TCP-MD5 or TCP-AO) to raise the bar for session spoofing, and consider inbound UPDATE filtering or policy to drop unexpected attributes - note these are hardening measures and do not fully prevent a legitimate, configured peer from sending the malformed UPDATE. Rate-limiting or damping BGP sessions can reduce blast radius but will not stop the rpd crash and may itself suppress legitimate routing updates; monitor rpd core files and BGP session flaps as detection signals.
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
Junos OS and Junos OS Evolved run routing protocols in a dedicated routing protocol daemon, rpd, which parses inbound BGP UPDATE messages and installs reachability into the routing table. The affected code path involves the interaction between ISO-VPN (an ISO/BGP VPN address-family configuration used to carry VPN reachability) and egress-protection (a Junos feature that pre-installs backup forwarding paths for protected egress links). When both features are active and a BGP UPDATE with specific attributes is received, a pointer that is expected to reference an egress-protection or ISO-VPN structure is left uninitialized/NULL and subsequently dereferenced, which is the CWE-476 root-cause class: a missing or insufficient NULL check on attacker-influenced parsed BGP data. Because rpd handles all routing protocols, the crash causes route churn and neighbor resets, degrading forwarding across the device rather than a bounded per-session failure. CPE data lists the wildcard entries cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:* and cpe:2.3:a:juniper_networks:junos_os_evolved:*:*:*:*:*:*:*:*, indicating the flaw is tracked across the Junos OS and Junos OS Evolved product lines; the configuration prerequisites narrow the practically exposed subset to devices running ISO-VPN plus egress-protection.
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
Reached over the network via a configured BGP peer with no authentication (PR:N, BGP unauthenticated) and low complexity; impact is a routing-daemon crash, so A:H with no confidentiality or integrity impact.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
3DescriptionCVE.org
A NULL Pointer Dereference vulnerability in the rpd routing daemon of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated configured BGP peer to cause a denial of service via a BGP UPDATE when ISO-VPN and egress-protection configuration is enabled.
Executive ViewAI
Juniper Networks Junos OS and Junos OS Evolved contain a high-severity (CVSS 8.7) flaw in the rpd routing daemon that allows a crafted BGP UPDATE from an already-configured peer to crash the routing process and disrupt network availability on devices where both ISO-VPN and egress-protection are enabled, a non-default configuration. Because there is no confidentiality or integrity loss, the exposure is one of service disruption rather than data compromise, and the attack surface is limited to operators' existing BGP peering relationships, not arbitrary internet hosts. Leadership should care because a successful trigger can interrupt routed traffic on affected Juniper platforms during a window in which no vendor patch is yet available, making configuration-based mitigation and peer monitoring the only near-term defenses.
No vendor-released patch identified at time of analysis. Interim mitigations: disable egress-protection or the ISO-VPN configuration on devices where the combination is not required; on devices where it must remain, restrict BGP peering to an explicit list of trusted, operator-configured peers and enable TCP-AO or MD5 authentication plus GTSM/TTL security on every adjacency; monitor for rpd process restarts, core files, and unexpected BGP session flaps; and apply vendor guidance as soon as it is issued.
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
A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).
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-101492
GHSA-mm2r-8hqh-vh2p
NVD
CVE.org
EPSS
VulDB
Exploit-DB