LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21910: Junos OS: EX4k Series, QFX5k Series: In an EVPN-VXLAN configuration link flaps cause Inter-VNI traffic drop

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21910 can cause traffic outages between VXLAN segments on certain Juniper EX4k and QFX5k switches. In specific EVPN-VXLAN LAG/VPLAG designs, a network-adjacent attacker can trigger link instability that makes inter-VNI traffic drop. Recovery may require restarting the affected forwarding component.

Executive priority

Prioritize for data centers using Juniper EVPN-VXLAN fabrics. The business risk is localized but potentially disruptive traffic loss between network segments. Patch during planned network maintenance, and prepare operational recovery steps for affected fabrics.

Technical view

The flaw is an improper exceptional-condition check in Junos OS PFE handling. It affects EX4k and QFX5k platforms supporting EVPN-VXLAN VPLAG, including listed QFX5110/5120/5200 and EX4100/4300/4400/4650. Conditions include EVPN-VXLAN LAG and multiple load-balanced next-hop routes to the same destination. CVSS v4.0 is 7.1.

Likely exposure

Exposure is limited to affected Junos OS releases on EX4k/QFX5k systems using EVPN-VXLAN VPLAG/LAG designs. Organizations without these platforms or configurations are likely not exposed based on the vendor description.

Exploitation context

The CVE describes unauthenticated, network-adjacent DoS potential. The source bundle does not indicate CISA KEV listing or active exploitation. The attacker must be positioned to cause relevant link flaps; impact is traffic loss, not code execution or data theft.

Researcher notes

Evidence is vendor-sourced. Scope depends heavily on platform and topology. The advisory names fixed release thresholds but does not provide broader workarounds beyond service restoration by restarting the affected FPC. No public exploit or active exploitation signal is provided in the supplied sources.

Mitigation direction

  • Upgrade affected Junos OS releases to the fixed versions named by Juniper.
  • Move all 22.2 deployments to a vendor-supported fixed release path.
  • Use FPC restart only for service restoration, not as permanent remediation.
  • Review Juniper JSA106009 before maintenance planning.

Validation and detection

  • Inventory EX4k and QFX5k switches and current Junos OS versions.
  • Identify EVPN-VXLAN VPLAG or LAG configurations on those platforms.
  • Check whether multiple load-balanced next-hop routes exist for same destinations.
  • Review outage logs for inter-VNI drops following link flaps.
  • Confirm remediation by verifying upgraded fixed releases are installed.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-754: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21910 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (4.0)
Known Exploited
No
Published

Vector: 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:U/RE:M/U:Green

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 4.0HighCVSS: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:U/RE:M/U:Green——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.1High
CVSS 4.0 vector shape for CVE-2026-21910Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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:U/RE:M/U:Green

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS0, 22.2, 22.4, 23.2, 23.4, 24.2, 24.4unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.