Unauthenticated network-adjacent RCE/DoS in Arista Wi‑Fi APs used in enterprise networks; can disrupt wireless access and allow persistent compromise across deployments.
CVE-2026-102162
Stack overflow in Arista Wi‑Fi gateway allows unauthenticated RCE or DoS via crafted packet.
Is CVE-2026-102162 being exploited?
Not confirmed. CVE-2026-102162 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-102162?
CVE-2026-102162 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102162?
Yes. A fix has been recorded for CVE-2026-102162. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102162 affect?
CVE-2026-102162 affects Arista Wi‑Fi access points with captive portal enabled, Arista APs with application firewall enabled on at least one SSID, Wireless gateway service on affected Arista APs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102162?
Isolate affected SSIDs, apply vendor mitigations, restrict access and install firmware updates when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Network-adjacent attacker can trigger a stack overflow to crash the wireless gateway (DoS) or execute arbitrary code, compromising APs and network access.
Immediate action required
- affected>= 22.0.0 and <= 22.0.1F-32
- affected>= 21.3.0 and <= 21.3.0M-13
- affected>= 1.0.0 and < 21.3.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.