Skip to main content

Junos OS EUVDEUVD-2026-101398

| CVE-2026-102183 HIGH
Improper Validation of Specified Quantity in Input (CWE-1284)
2026-10-14 juniper GHSA-3wgj-r8j2-5467
8.7
CVSS 4.0 · Vendor: juniper
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Establish/compromise configured BGP EVPN peer
  2. Delivery
    Craft malformed NLRI in BGP UPDATE
  3. Exploit
    Trigger input-quantity validation flaw in rpd
  4. Execution
    rpd daemon crashes
  5. Impact
    Routing disruption / denial of service

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V2 - Validation and Business Logic Input size validation
Exploitation Conditions

The target must be running an affected Junos OS or Junos OS Evolved release AND be configured with BGP EVPN with at least one established peering session. Exploitation requires the attacker to act as a configured BGP EVPN peer (control of a legitimate peer, a compromised peer, or on-path injection into the EVPN session) and to send a specifically malformed NLRI. This is the primary limiting factor: devices without BGP EVPN configured are not affected, and the flaw is not reachable from arbitrary untrusted hosts - only from within the EVPN peering trust boundary. No user interaction or authentication credentials on the target are required beyond the existing peer relationship, and recovery is automatic (R:A) after the rpd restart.

Impact

This is a legitimately serious availability threat but not a universal-panic issue. The CVSS 4.0 score of 8.7 (High) is driven entirely by availability impact (VA:H) with no confidentiality or integrity impact - it is a pure denial-of-service: a malformed BGP EVPN NLRI crashes the routing protocol daemon (rpd). The vector shows AV:N/AC:L/PR:N/UI:N, and the supplemental metrics AU:Y (automatable) and V:C (concentrated value) indicate the attack can be scripted and reliably reproduced, which raises operational concern. However, the practical gating factor is that the attacker must be a CONFIGURED BGP EVPN peer - exploitation is not possible from an arbitrary internet host, only from a device that already has an established EVPN peering relationship (or an on-path attacker able to inject into that session). This materially reduces real-world exposure versus the raw PR:N rating. No EPSS score, KEV listing, or public POC is present in the provided data, so there is no evidence of active or widespread exploitation. Net: prioritize patching on EVPN-enabled Junos devices (trust-boundary DoS with easy, repeatable trigger and automatic recovery per R:A), but this is not an unauthenticated-from-anywhere RCE and does not warrant emergency out-of-band response absent exposure to untrusted BGP peers.

Exploit ScenarioDerived

An attacker who controls or has compromised a device configured as a BGP EVPN peer of a vulnerable Junos OS / Junos OS Evolved router sends a specifically malformed NLRI in a BGP UPDATE. The rpd daemon fails to properly validate the specified quantity in the input and crashes, disrupting routing on the target. No public exploit code was identified at time of analysis, but the condition is trivially repeatable once a peering session exists.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Malformed BGP EVPN NLRI sent to the routing protocol daemon (rpd) crashes rpd on Juniper Networks Junos OS and Junos OS Evolved, disrupting routing on the affected device until the daemon restarts automatically (CVSS 4.0 base 8.7; assessed CVSS 3.1 7.5 with availability-only impact). Only devices that have BGP EVPN configured with an established peering session are reachable: the attacker must act as a configured BGP EVPN peer - a controlled or compromised peer, or an on-path injection into that session - and needs no credentials or user interaction on the target (PR:N/UI:N). Affected releases span multiple Junos OS and Junos OS Evolved branches (23.2 through 26.2), and no public exploit code or confirmed active exploitation was identified at time of analysis; a vendor patch is available.

RemediationAI

Vendor-released patches are available: Juniper Junos OS is fixed in 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, while Junos OS Evolved is fixed in 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, 26.2R1-S2-EVO, 25.4X300-D40-EVO, and 25.2X100-D35-EVO (see Juniper advisory JSA112187, https://supportportal.juniper.net/JSA112187). Upgrade to the maintenance release on the branch in use, and note that the EUVD listing shows Junos OS Evolved 23.4X100 without a published fixed build, so that platform should be moved to a supported branch rather than waiting on a maintenance fix. Where immediate upgrade is not possible, reduce exposure by removing BGP EVPN configuration from devices that do not require it, restricting EVPN peering to a minimal set of explicitly trusted neighbors, and hardening session integrity - TCP-MD5 or TCP-AO plus strict TTL/GTSM and prefix filters - so that an attacker cannot easily assume or inject into the peer role; these controls shrink attack surface but do not eliminate the parsing defect and are not a substitute for patching, and applying strict NLRI/route-type filtering may drop legitimate EVPN routes. Because the crash is limited to rpd and recovery is automatic (R:A), operational impact can also be contained by ensuring EVPN peerings and routing adjacencies are distributed across redundant routing engines or upstream devices so a single rpd restart does not isolate a network segment.

Affected VersionsENISA

Junos OS 24.2 <24.2R2-S5.5
Junos OS 24.4 <24.4R2-S5
Junos OS Evolved 25.2 <25.2R2-S2-EVO
Junos OS Evolved 0 <23.2R2-S7.7-EVO
Junos OS Evolved 23.4 <23.4R2-S8.11-EVO
Junos OS Evolved 25.4X300 <25.4X300-D40-EVO
Junos OS 0 <23.2R2-S7.7
Junos OS 25.2 <25.2R2-S2
Junos OS Evolved 24.2 <24.2R2-S5.6-EVO
Junos OS Evolved 23.4X100
Junos OS 25.4 <25.4R1-S3
Junos OS Evolved 25.4 <25.4R1-S3-EVO
Junos OS 23.4 <23.4R2-S8.13
Junos OS 26.2 <26.2R1-S2
Junos OS Evolved 25.2X100 <25.2X100-D35-EVO
Junos OS Evolved 24.4 <24.4R2-S5-EVO
Junos OS Evolved 26.2 <26.2R1-S2-EVO

Affected Packages

euvd junos_os fix: 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, 26.2R1-S2
euvd junos_os_evolved fix: 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.2X100-D35-EVO, 25.4R1-S3-EVO, 25.4X300-D40-EVO, 26.2R1-S2-EVO

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 flaw is an instance of CWE-1284 (Improper Validation of Specified Quantity in Input) inside rpd, the Juniper routing protocol daemon that implements BGP and its multiprotocol extensions. EVPN routes are carried over MP-BGP using the EVPN address family (AFI/SAFI 25) and encoded as NLRI, which are length-prefixed structures containing route-type-specific fields such as route distinguishers, Ethernet segment identifiers, MAC/IP advertisement data, and label stacks. CWE-1284 covers the class of bugs where a length, count, or size field inside such a structure is trusted and used to drive a buffer, memory operation, or loop without adequate validation - here a specifically malformed NLRI causes rpd to fault rather than reject the update. The affected CPEs (cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved) cover both the classic FreeBSD-based Junos OS and the Linux-based Junos OS Evolved, which share the rpd code base, so both platforms require the corresponding patched releases. Per the independent assessment, the practical blast radius is bounded by configuration: the malformed NLRI must arrive from within an established EVPN peering relationship, so the defect is not reachable from arbitrary untrusted hosts, and the impact is confined to availability (VC:N/VI:N, VA:H) because rpd recovers automatically after the crash.

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

Vendor (juniper) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/AU:Y/R:A/V:C/RE:M
vuln.today AI 7.5 HIGH

Network-reachable via BGP session with low complexity and no target privileges (PR:N), but impact is availability-only (rpd crash) so C:N/I:N/A:H and scope unchanged.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (juniper).

CVSS VectorVendor: juniper

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch available
Oct 14, 2026 - 18:05 EUVD
CVSS changed
Oct 14, 2026 - 17:22 NVD
7.5 (HIGH) 8.7 (HIGH)
CVE Published
Oct 14, 2026 - 16:58 cve.org
HIGH 8.7

DescriptionCVE.org

An Improper Validation of Specified Quantity in Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a configured BGP EVPN peer to cause an rpd crash via a specifically malformed NLRI.

Executive ViewAI

Why It Matters

Juniper Networks Junos OS and Junos OS Evolved releases 23.2 through 26.2 can be disrupted by a malformed BGP EVPN routing advertisement that crashes the routing protocol daemon (rpd) on any device with an established EVPN peering session, halting routing on that device until the daemon restarts automatically. The exposure is limited to organizations running EVPN-based data center or service provider fabrics, and exploiting it requires the attacker to already hold a configured BGP EVPN peer position or to inject into that live session - unauthenticated (PR:N/UI:N) with no user interaction, but not remotely reachable from the open internet. Leadership should care because a successful event produces unplanned availability outages in the fabrics that carry production and customer traffic, while remediation is otherwise a routine vendor-patch exercise.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 62% exploitable
Prevalence
High
Juniper Junos widely deployed in enterprise and carrier networks
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Medium
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2026-102059 HIGH
8.7 Oct 14

OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u

CVE-2026-101956 CRITICAL
9.3 Oct 14

Unauthenticated remote code execution with root privileges affects Juniper Networks Junos OS devices that expose the J-W

CVE-2026-102175 CRITICAL
9.3 Oct 14

Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow

CVE-2026-33792 CRITICAL
9.3 Oct 14

A stack-based buffer overflow in the srxpfe packet forwarding process of Juniper Networks Junos OS on SRX Series devices

CVE-2026-101986 CRITICAL
9.3 Oct 14

Unauthenticated remote code execution with elevated privileges is possible in Juniper Junos OS and Junos OS Evolved thro

CVE-2026-101982 CRITICAL
9.3 Oct 14

Remote root code execution in the routing protocol daemon (rpd) of Juniper Junos OS is reachable through protocol-valid

CVE-2026-101990 CRITICAL
9.3 Oct 14

Remote code execution (on Junos OS) and rpd denial of service (on Junos OS and Junos OS Evolved) result from a stack-bas

CVE-2026-33796 CRITICAL
9.3 Oct 14

Remote code execution with root privileges on Juniper Networks Junos OS and Junos OS Evolved is possible when the routin

CVE-2026-101983 CRITICAL
9.3 Oct 14

Remote code execution and denial of service in Juniper Networks Junos OS and Junos OS Evolved arise from a stack-based b

CVE-2026-101954 CRITICAL
9.3 Oct 14

Unauthenticated remote attackers can gain root-level configuration access and fully compromise Juniper Junos OS and Juno

CVE-2026-101980 CRITICAL
9.3 Oct 14

Integer underflow in the Junos OS kernel can crash a device when the Extended Echo feature (RFC 8335 ICMP probing) is co

CVE-2026-101950 CRITICAL
9.3 Oct 14

Heap-based buffer overflow in Juniper Networks Junos OS on SRX Series devices that have Secure Vector Routing (SVR) enab

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy