Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain Layer-2 adjacency to MX router
-
DeliveryCraft malformed MAP-T / MPLS-over-GRE packet
-
ExploitPFE miscalculates packet size
-
ExecutionMQSS TAIL length overflow major error
-
ImpactFPC reset drops all line-card traffic
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Input size validation
|
| Exploitation Conditions | Exploitation requires Layer-2 adjacency - the attacker must be in the same broadcast domain as the target MX router to deliver the crafted packet (AV:A), so it is not remotely routable across the internet. The affected system must also be processing MAP-T traffic OR non-IP traffic encapsulated in IP such as MPLS over GRE; routers not configured for these encapsulations do not enter the vulnerable PFE code path. No authentication and no user interaction are needed (PR:N/UI:N) and no special conditions beyond adjacency and the feature being in use. Limiting factors: required Layer-2 network position, dependence on the non-default MAP-T / IP-encapsulated-non-IP forwarding features, restriction to MX Series hardware, and automatic FPC recovery which bounds each hit to a transient (not permanent) outage. |
| Impact | The vendor CVSS 4.0 base score is 7.1 (High) with vector AV:A/AC:L/PR:N/UI:N and availability-only impact (VA:H, SA:L). The adjacent attack vector (AV:A) is the key limiter: the attacker must sit in the same broadcast domain / Layer-2 segment, which sharply narrows the threat population versus a network-routable (AV:N) bug, but AC:L and PR:N mean no authentication and no special timing once adjacency is achieved, and AU:Y indicates the attack is automatable. Impact is availability-only - no confidentiality or integrity loss - and Junos automatically resets and recovers the FPC (R:A), so this is a transient disruption rather than persistent compromise, though a sustained packet stream could repeatedly reset the FPC for a rolling outage. No EPSS score, KEV entry, or public POC is present in the provided data, so real-world exploitation risk is currently low-to-moderate and gated by network position. Signals are internally consistent: this is a legitimate availability priority for exposed MX edge devices but not a drop-everything internet-facing RCE. |
| Exploit ScenarioDerived | An attacker with a foothold on a host or device in the same broadcast domain as an MX Series router (for example a compromised server on an access VLAN, or a rogue device on a peering segment) crafts a single packet in the affected MAP-T or MPLS-over-GRE format and sends it toward the router. The PFE miscomputes the packet size, raises an MQSS major error, and the FPC resets, dropping all traffic on that line card until it recovers; repeating the packet produces a sustained outage. No authentication is required and the attack is automatable, but no public POC is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jul 09, 2026
Denial-of-service in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series routers lets an unauthenticated, Layer-2 adjacent attacker crash a line card by sending a single crafted packet within the same broadcast domain. The affected system miscalculates the packet size (CWE-1284, improper validation of specified quantity in input), which fails downstream processing and raises an MQSS major CMError that forces an automatic FPC reset, interrupting all traffic on that FPC until it recovers. Only deployments handling MAP-T or non-IP-over-IP traffic (e.g. MPLS over GRE) are exposed; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Earlier versions of this analysis (2)
Denial-of-service in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series routers allows an unauthenticated, Layer-2-adjacent attacker to crash a line card by sending a single crafted packet. The device miscalculates the packet size, causing packet processing to fail and triggering an MQSS 'Unroll TAIL length overflow' major error (MQSS_CMERROR_LI_INT_REG_UNROLL_TAIL_LENGTH_OVF) that resets the affected FPC and drops all traffic on it until it auto-recovers. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the low attack complexity and lack of authentication make it a meaningful availability risk for exposed MX deployments using MAP-T or IP-encapsulated non-IP traffic.
Denial-of-service in Juniper Networks Junos OS on MX Series routers allows an unauthenticated attacker with L2 adjacency to force Flexible PIC Concentrator (FPC) resets by sending a specially crafted packet in the same broadcast domain. Exploitation is gated by specific encapsulation configurations - MAP-T or non-IP-over-IP such as MPLS over GRE - under which the Packet Forwarding Engine miscalculates packet size, triggering a major MQSS hardware error and FPC reset that disrupts traffic until automatic recovery completes. No public exploit code exists and this vulnerability is not listed in CISA KEV; however, the unauthenticated adjacent attack vector is operationally realistic in ISP peering and carrier edge environments.
RemediationAI
Vendor-released patch: upgrade Junos OS on MX Series to a fixed release - 23.2R2-S6, 23.4R2-S7, 24.2R2-S4, 24.4R2-S4, or 25.2R2 (or later) per Juniper advisory JSA110079 (https://supportportal.juniper.net/JSA110079). Where immediate patching is not possible, reduce exposure by constraining the Layer-2 adjacency an attacker needs: because the trigger is an adjacent (same-broadcast-domain) packet, restrict which devices share the affected interfaces' broadcast domains and apply strict port security / VLAN segmentation on access-facing ports so untrusted hosts cannot inject the crafted frames. If operationally feasible and the features are not required, disabling MAP-T or the non-IP-over-IP (e.g. MPLS-over-GRE) forwarding paths removes the vulnerable code path, but this will break any services that depend on those encapsulations, so validate the traffic profile before making the change. No configuration workaround fully mitigates while those features remain in use, so patching is the definitive fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package 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 lives in the MX Series Packet Forwarding Engine's MQSS (memory and queuing subsystem) ASIC path, specifically the 'Unroll TAIL length' logic (register MQSS_CMERROR_LI_INT_REG_UNROLL_TAIL_LENGTH_OVF, 0x2205eb). When a packet in an affected encapsulation format is processed, the PFE computes an incorrect packet size, producing a TAIL length overflow. CWE-1284 (Improper Validation of Specified Quantity in Input) is the root-cause class: a length/size field derived from the packet is trusted without proper bounds validation, so an oversized or malformed length value overflows internal processing state. Because MAP-T (Mapping of Address and Port using Translation) and IP-encapsulated non-IP payloads such as MPLS-over-GRE take special forwarding paths, only those code paths trigger the miscalculation. The CPE (cpe:2.3:a:juniper_networks:junos_os:*) confirms Junos OS broadly, but the vendor scopes impact to MX Series hardware running the listed trains.
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/RE:M
Adjacent Layer-2 delivery (AV:A) with no auth or interaction and low complexity, causing availability-only impact via FPC reset (A:H, C/I:N); scope unchanged as impact stays within the router.
Primary rating from Vendor (juniper).
CVSS VectorVendor: juniper
Lifecycle Timeline
4DescriptionCVE.org
An Improper Validation of Specified Quantity in Input vulnerability in the Packet Forwarding Engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS).
When a specific packet is received from device in the same broadcast domain, an affected system calculates the packet size incorrectly. This causes further packet processing to fail, which triggers an FPC major error, resulting in a FPC reset impacting traffic until the FPC has automatically recovered.
Affected scenarios are: MAP-T, or non-IP traffic encapsulated in IP (e.g. MPLS over GRE).
When this issue happens the following logs can be observed:
fpc<#> CMError: /fpc/0/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_LI_INT_REG_UNROLL_TAIL_LENGTH_OVF (0x2205eb), scope: pfe, category: functional, severity: major, module: MQSS(0), type: LI: Unroll TAIL length overflow, oc_category: default fpc<#> Performing action reset-fru for error /fpc/0/pfe/0/cm/0/MQSS(0)/0/MQSS_CMERROR_LI_INT_REG_UNROLL_TAIL_LENGTH_OVF (0x2205eb) in module: MQSS(0) with scope: pfe category: functional level: major, oc_category: default
This issue affects Junos OS on MX Series:
- all versions before 23.2R2-S6,
- 23.4 versions before 23.4R2-S7,
- 24.2 versions before 24.2R2-S4,
- 24.4 versions before 24.4R2-S4,
- 25.2 versions before 25.2R2.
Articles & Coverage 1
Executive ViewAI
A vulnerability in Juniper Junos OS MX Series routers enables unauthenticated attackers with Layer-2 network access to crash line cards through malformed packet processing, causing traffic interruption. Organizations operating these routers with MAP-T or specialized traffic types face service availability risks that persist until the affected line card recovers. Leadership should prioritize assessment of network exposure and implementation of access controls.
Absent vendor patch, implement Layer-2 access controls and network segmentation to prevent unauthenticated packet injection into broadcast domains. Deploy port security, VLAN access control lists, or MAC-based authentication on adjacent network segments. Configure line card traffic rate limiting or packet inspection to detect malformed packets. Restrict direct Layer-2 connectivity to MX Series infrastructure.
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 buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
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-42706
GHSA-qwhr-x4c6-c5hc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB