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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.5, indicating it requires adjacent network access with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 12 products from juniper, from juniper, from juniper and 9 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-07-09T22:17:06.707
2026-07-13T20:58:26.287
Analyzed
CVSSv3.1: 6.5 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | < 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.2 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 23.4 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.2 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 24.4 | Yes |
| Operating System | juniper | junos | 25.2 | Yes |
| Operating System | juniper | junos | 25.2 | Yes |
| Operating System | juniper | junos | 25.2 | Yes |
| Operating System | juniper | junos | 25.2 | Yes |
| Hardware | juniper | mx10004 | - | No |
| Hardware | juniper | mx10008 | - | No |
| Hardware | juniper | mx2008 | - | No |
| Hardware | juniper | mx2010 | - | No |
| Hardware | juniper | mx2020 | - | No |
| Hardware | juniper | mx204 | - | No |
| Hardware | juniper | mx240 | - | No |
| Hardware | juniper | mx301 | - | No |
| Hardware | juniper | mx304 | - | No |
| Hardware | juniper | mx480 | - | No |
| Hardware | juniper | mx960 | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.