CVE-2026-21910: CWE-754 Improper Check for Unusual or Exceptional Conditions in Juniper Networks Junos OS
An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on EX4k Series and QFX5k Series platforms allows an unauthenticated network-adjacent attacker flapping an interface to cause traffic between VXLAN Network Identifiers (VNIs) to drop, leading to a Denial of Service (DoS). On all EX4k and QFX5k platforms, a link flap in an EVPN-VXLAN configuration Link Aggregation Group (LAG) results in Inter-VNI traffic dropping when there are multiple load-balanced next-hop routes for the same destination. This issue is only applicable to systems that support EVPN-VXLAN Virtual Port-Link Aggregation Groups (VPLAG), such as the QFX5110, QFX5120, QFX5200, EX4100, EX4300, EX4400, and EX4650. Service can only be restored by restarting the affected FPC via the 'request chassis fpc restart slot <slot-number>' command. This issue affects Junos OS on EX4k and QFX5k Series: * all versions before 21.4R3-S12, * all versions of 22.2 * from 22.4 before 22.4R3-S8, * from 23.2 before 23.2R2-S5, * from 23.4 before 23.4R2-S5, * from 24.2 before 24.2R2-S3, * from 24.4 before 24.4R2.
AI Analysis
Technical Summary
CVE-2026-21910 is a vulnerability classified under CWE-754 (Improper Check for Unusual or Exceptional Conditions) found in the packet forwarding engine (PFE) of Juniper Networks Junos OS on EX4k and QFX5k Series platforms. These platforms include models such as QFX5110, QFX5120, QFX5200, EX4100, EX4300, EX4400, and EX4650 that support EVPN-VXLAN Virtual Port-Link Aggregation Groups (VPLAG). The vulnerability is triggered when an unauthenticated network-adjacent attacker induces a link flap on an interface configured with EVPN-VXLAN LAG. This causes the PFE to improperly handle the exceptional condition, leading to dropped traffic between VXLAN Network Identifiers (VNIs) when multiple load-balanced next-hop routes exist for the same destination. The root cause is an improper check in the PFE logic that fails to maintain traffic forwarding under these conditions. The impact is a denial of service (DoS) affecting availability but not confidentiality or integrity. Recovery requires a manual restart of the affected Flexible PIC Concentrator (FPC) using the 'request chassis fpc restart slot <slot-number>' command. The vulnerability affects all Junos OS versions before 21.4R3-S12, all 22.2 versions, and certain releases up to 24.4R2. No public exploits or active exploitation have been reported. The CVSS v3.1 score is 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating medium severity with network-adjacent attack vector, low attack complexity, no privileges or user interaction required, and high impact on availability.
Potential Impact
For European organizations, especially those operating data centers, cloud infrastructure, or enterprise networks using Juniper EX4k and QFX5k Series switches with EVPN-VXLAN VPLAG configurations, this vulnerability poses a risk of network disruption and service outages. The denial of service can interrupt critical inter-VNI traffic, potentially impacting multi-tenant environments, data center fabrics, and service provider networks. This can degrade business continuity, affect customer-facing services, and cause operational downtime. Since the attack requires network adjacency but no authentication or user interaction, it could be exploited by malicious insiders or attackers who gain access to the local network segment. The need for manual intervention to restore service increases operational overhead and response time. Although confidentiality and integrity are not impacted, availability degradation in core network infrastructure can have cascading effects on dependent services and applications. Organizations relying on these Juniper platforms for high availability and scalable VXLAN deployments should prioritize remediation to avoid potential service disruptions.
Mitigation Recommendations
1. Upgrade Junos OS to the latest patched versions starting from 21.4R3-S12 or later releases that address this vulnerability, ensuring all affected devices are updated promptly. 2. Implement network segmentation and strict access controls to limit network adjacency exposure, reducing the attack surface for unauthenticated attackers. 3. Monitor interface status and link flap events closely using network management tools and SNMP traps to detect abnormal interface behavior indicative of exploitation attempts. 4. Automate alerting and response workflows to quickly identify and remediate link flapping issues before they cause traffic disruption. 5. Prepare operational procedures for rapid FPC restart to restore service if a DoS occurs, minimizing downtime. 6. Review and validate EVPN-VXLAN LAG configurations to ensure they follow best practices and avoid unnecessary complexity that could exacerbate failure conditions. 7. Engage with Juniper support for additional guidance and consider deploying redundant paths or failover mechanisms to maintain availability during incidents. 8. Conduct regular vulnerability assessments and penetration testing focusing on network infrastructure to identify and mitigate similar risks proactively.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland, Belgium, Switzerland
CVE-2026-21910: CWE-754 Improper Check for Unusual or Exceptional Conditions in Juniper Networks Junos OS
Description
An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on EX4k Series and QFX5k Series platforms allows an unauthenticated network-adjacent attacker flapping an interface to cause traffic between VXLAN Network Identifiers (VNIs) to drop, leading to a Denial of Service (DoS). On all EX4k and QFX5k platforms, a link flap in an EVPN-VXLAN configuration Link Aggregation Group (LAG) results in Inter-VNI traffic dropping when there are multiple load-balanced next-hop routes for the same destination. This issue is only applicable to systems that support EVPN-VXLAN Virtual Port-Link Aggregation Groups (VPLAG), such as the QFX5110, QFX5120, QFX5200, EX4100, EX4300, EX4400, and EX4650. Service can only be restored by restarting the affected FPC via the 'request chassis fpc restart slot <slot-number>' command. This issue affects Junos OS on EX4k and QFX5k Series: * all versions before 21.4R3-S12, * all versions of 22.2 * from 22.4 before 22.4R3-S8, * from 23.2 before 23.2R2-S5, * from 23.4 before 23.4R2-S5, * from 24.2 before 24.2R2-S3, * from 24.4 before 24.4R2.
AI-Powered Analysis
Technical Analysis
CVE-2026-21910 is a vulnerability classified under CWE-754 (Improper Check for Unusual or Exceptional Conditions) found in the packet forwarding engine (PFE) of Juniper Networks Junos OS on EX4k and QFX5k Series platforms. These platforms include models such as QFX5110, QFX5120, QFX5200, EX4100, EX4300, EX4400, and EX4650 that support EVPN-VXLAN Virtual Port-Link Aggregation Groups (VPLAG). The vulnerability is triggered when an unauthenticated network-adjacent attacker induces a link flap on an interface configured with EVPN-VXLAN LAG. This causes the PFE to improperly handle the exceptional condition, leading to dropped traffic between VXLAN Network Identifiers (VNIs) when multiple load-balanced next-hop routes exist for the same destination. The root cause is an improper check in the PFE logic that fails to maintain traffic forwarding under these conditions. The impact is a denial of service (DoS) affecting availability but not confidentiality or integrity. Recovery requires a manual restart of the affected Flexible PIC Concentrator (FPC) using the 'request chassis fpc restart slot <slot-number>' command. The vulnerability affects all Junos OS versions before 21.4R3-S12, all 22.2 versions, and certain releases up to 24.4R2. No public exploits or active exploitation have been reported. The CVSS v3.1 score is 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating medium severity with network-adjacent attack vector, low attack complexity, no privileges or user interaction required, and high impact on availability.
Potential Impact
For European organizations, especially those operating data centers, cloud infrastructure, or enterprise networks using Juniper EX4k and QFX5k Series switches with EVPN-VXLAN VPLAG configurations, this vulnerability poses a risk of network disruption and service outages. The denial of service can interrupt critical inter-VNI traffic, potentially impacting multi-tenant environments, data center fabrics, and service provider networks. This can degrade business continuity, affect customer-facing services, and cause operational downtime. Since the attack requires network adjacency but no authentication or user interaction, it could be exploited by malicious insiders or attackers who gain access to the local network segment. The need for manual intervention to restore service increases operational overhead and response time. Although confidentiality and integrity are not impacted, availability degradation in core network infrastructure can have cascading effects on dependent services and applications. Organizations relying on these Juniper platforms for high availability and scalable VXLAN deployments should prioritize remediation to avoid potential service disruptions.
Mitigation Recommendations
1. Upgrade Junos OS to the latest patched versions starting from 21.4R3-S12 or later releases that address this vulnerability, ensuring all affected devices are updated promptly. 2. Implement network segmentation and strict access controls to limit network adjacency exposure, reducing the attack surface for unauthenticated attackers. 3. Monitor interface status and link flap events closely using network management tools and SNMP traps to detect abnormal interface behavior indicative of exploitation attempts. 4. Automate alerting and response workflows to quickly identify and remediate link flapping issues before they cause traffic disruption. 5. Prepare operational procedures for rapid FPC restart to restore service if a DoS occurs, minimizing downtime. 6. Review and validate EVPN-VXLAN LAG configurations to ensure they follow best practices and avoid unnecessary complexity that could exacerbate failure conditions. 7. Engage with Juniper support for additional guidance and consider deploying redundant paths or failover mechanisms to maintain availability during incidents. 8. Conduct regular vulnerability assessments and penetration testing focusing on network infrastructure to identify and mitigate similar risks proactively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- juniper
- Date Reserved
- 2026-01-05T17:32:48.710Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69694e771ab3796b1050014b
Added to database: 1/15/2026, 8:30:47 PM
Last enriched: 1/15/2026, 8:47:33 PM
Last updated: 1/15/2026, 9:31:01 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-65368: n/a
MediumCVE-2025-67025: n/a
MediumCVE-2026-21921: CWE-416 Use After Free in Juniper Networks Junos OS
MediumCVE-2026-21920: CWE-252 Unchecked Return Value in Juniper Networks Junos OS
HighCVE-2026-21918: CWE-415 Double Free in Juniper Networks Junos OS
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.