Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain Layer 2 adjacency to MVRP interface
-
DeliveryCraft malformed MVRP Ethernet frame
-
ExploitTrigger input inconsistency in l2cpd
-
ExecutionDisrupt Layer 2 control protocols
-
ImpactDenial of service on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Hardware validation bypass
|
| Exploitation Conditions | Exploitation requires that MVRP (Multiple VLAN Registration Protocol) is explicitly enabled on at least one interface - this is a non-default Layer 2 feature, so devices without MVRP configured are not exposed. The attacker must also have Layer 2 adjacency (AV:A): direct access to the same broadcast domain/VLAN as the MVRP-enabled interface, meaning the frame cannot be routed across Layer 3 boundaries or exploited remotely over the Internet. No authentication is required (PR:N) and no user interaction (UI:N). The combination of mandatory MVRP configuration plus adjacency is the primary factor limiting real-world exploitability; impact is confined to availability of Layer 2 control protocols on the affected device (VC/VI:N). |
| Impact | This is a genuine but bounded operational risk rather than a top-tier emergency. The only provided scoring is a CVSS 4.0 vector (7.1) with AV:A (adjacent/Layer 2), AC:L, AT:N, PR:N, UI:N and impact limited to availability (VA:H, with subsequent-system SA:L and VC/VI/VA confidentiality/integrity all N) - consistent with the description of a denial of service in Layer 2 control protocols, not code execution or data exposure. The adjacency requirement (AV:A) is the single most important limiting signal: an attacker must already be on the same Layer 2 segment/broadcast domain as an MVRP-enabled interface, which excludes remote Internet-based exploitation and sharply narrows the threat population to insiders, compromised adjacent devices, or attackers with physical/VLAN access. No EPSS score, KEV listing, or POC was provided in the input, so exploitation probability cannot be quantified from this data; absence of KEV/POC is not proof of safety but indicates no confirmed active exploitation or public exploit at analysis time. There is no conflicting data between the vector and description - both agree on adjacent, unauthenticated, availability-only impact. Net: a credible DoS against network infrastructure that should be patched on a normal maintenance cadence, prioritized higher only where MVRP is actually enabled on exposed/untrusted Layer 2 segments. |
| Exploit ScenarioDerived | An attacker with Layer 2 adjacency to a Junos or Junos OS Evolved device (e.g., a rogue or compromised host on the same VLAN/broadcast domain) sends a crafted MVRP Ethernet frame to an MVRP-enabled interface. The malformed frame triggers an input-consistency validation flaw in the l2cpd process, disrupting associated Layer 2 control protocols and causing a denial of service. No public exploit code was identified in the provided data, 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
A crafted MVRP Ethernet frame sent to an MVRP-enabled interface can crash or disrupt the l2cpd Layer 2 control-protocol daemon in Juniper Networks Junos OS and Junos OS Evolved, causing a denial of service for associated Layer 2 control protocols. Only devices with MVRP (Multiple VLAN Registration Protocol) explicitly enabled on at least one interface, and reachable from the same Layer 2 broadcast domain, are exposed - MVRP is not enabled by default, so the vast majority of deployments are not at risk. No authentication or user interaction is required, but the attacker must have Layer 2 adjacency; the frame cannot be delivered across a Layer 3 boundary or over the internet. Scoring is AV:A with high availability impact only (C:N/I:N per the independent CVSS 3.1 assessment); there is no public exploit identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to the fixed Junos OS release for your train - 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3 or 26.2R1-S2 - or the corresponding Junos OS Evolved build - 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 or 26.2R1-S2-EVO (with the matching X100/X300 platform builds listed in JSA112187). Details and the full fixed-release table are in the vendor advisory at https://supportportal.juniper.net/JSA112187. If immediate upgrade is not possible, the most effective compensating control is to disable MVRP on all interfaces that do not require it, since the vulnerability is only reachable when MVRP is enabled; the trade-off is loss of dynamic VLAN registration, which must be replaced by static VLAN configuration on those links. Because exploitation requires Layer 2 adjacency, restricting the attack surface matters: disable MVRP on edge or untrusted-facing ports, apply the MVRP profile only to trusted trunk links, and enforce Layer 2 access controls (802.1X, MAC limiting/port security, or dedicated VLANs) so untrusted hosts cannot reach an MVRP-enabled interface. These are containment measures that reduce exposure rather than eliminate the parsing defect, so scheduling the vendor patch remains the definitive fix.
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 flaw is CWE-1288, Improper Validation of Consistency within Input, and lives in Juniper's l2cpd daemon, the process that implements Layer 2 control protocols on Junos OS and Junos OS Evolved. MVRP, defined by IEEE 802.1ak as an amendment to 802.1Q, uses MRP (Multiple Registration Protocol) attribute messages to propagate VLAN registrations across a bridged domain; the protocol exchanges MRPDUs with encoded attribute lists that a receiver must parse for internal consistency (attribute type, length, event, vector encoding). Because l2cpd does not adequately validate the consistency of the fields inside a received MVRP frame, a malformed MRPDU delivered to an MVRP-enabled interface can drive the daemon into an invalid state and terminate or destabilize it, which in turn affects the Layer 2 control protocols it serves. Affected CPEs identify the two impacted product families - cpe:2.3:a:juniper_networks:junos_os and cpe:2.3:a:juniper_networks:junos_os_evolved - spanning multiple release trains (23.2, 23.4, 24.2, 24.4, 25.2, 25.4, 26.2 for Junos OS, plus Evolved and X100/X300 variants). The exposure is inherently link-local: MVRP frames are not routable, so the attack surface is limited to hosts on the same VLAN or broadcast segment as the MVRP-enabled interface.
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/AU:Y/R:A/V:C/RE:M
Adjacent Layer 2 attacker (AV:A) with no auth or interaction (PR:N/UI:N), low complexity, causing availability-only DoS (A:H) with no confidentiality or integrity impact.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
4DescriptionCVE.org
An Improper Validation of Consistency within Input vulnerability in the l2cpd process of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent unauthenticated Layer 2 attacker to cause a denial of service in associated Layer 2 control protocols via a crafted MVRP Ethernet frame sent to an MVRP-enabled interface.
Executive ViewAI
Juniper Networks Junos OS and Junos OS Evolved contain a high-severity vulnerability that allows an attacker with Layer 2 network access to crash the l2cpd daemon, disrupting Layer 2 control protocols and causing a denial of service. Only organizations that have explicitly enabled MVRP on at least one interface are exposed, and because MVRP is not enabled by default, most deployments are unaffected. Leadership should direct network teams to verify MVRP usage and apply the vendor patch to prevent potential outages in affected network segments.
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-101371
GHSA-w88x-j48x-p6wf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB