CVE-2026-7473: Arista EOS tunnel decapsulation validation flaw
Tech GuruQuick Answer
CVE-2026-7473 lets affected Arista EOS switches decapsulate unexpected tunnel protocols sent to a configured decapsulation IP. Advisory 0137 does not offer a fixed EOS release or hotfix; its resolution is the documented ACL mitigation. Identify the platform and tunnel configuration, then plan the appropriate filters with Arista's shared-IP and TCAM cautions. Preserve unexpected forwarding evidence; KEV membership does not prove a particular switch was exploited.
Fix Or Immediate Action
What to do now: Confirm the platform and configured tunnel endpoints, then apply advisory 0137's ACL mitigation and validate permitted and rejected traffic. Arista plans no software upgrade path or hotfix for this issue.
Evidence check: Vendor evidence and unresolved source limits are described below. CISA KEV catalog 2026.10.02 was checked on October 2. Preserve the distinction between vendor publication history, catalog dates and evidence from your deployment; no patch or exploit test is claimed.
Context
Scope And Impact In Plain Language
Who should check: Anyone who manages Arista Extensible Operating System.
When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.
What could happen: The product may make the wrong security decision when comparing crafted data, allowing traffic, input, or an action that should have been rejected.
Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.
Status At A Glance
| Product scope | Arista — Extensible Operating System |
|---|---|
| CVE | CVE-2026-7473 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-06-09 |
| Vendor severity | Medium |
| CVSS | CVSS 3.1 base 5.8 |
| Ransomware field | Unknown — this is not the same as No; CISA has not marked the field Known. |
| Forensic-triage field | No in the current CISA field; organizations should still investigate when exposure or evidence warrants it. |
| CWE | CWE-1023 |
| Federal remediation date | 2026-06-23 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Arista Extensible Operating System Incomplete Comparison with Missing Factors Vulnerability. Arista Extensible Operating System (EOS) contains an incomplete comparison with missing factors vulnerability when the switch incorrectly decapsulate and forwards other unexpected tunneled packet with a destination IP matching its configured decapsulation IP. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.
Affected Scope
Advisory 0137 lists 7020R, 7280R/R2 and 7500R/R2; 7280R3, 7500R3 and 7800R3 have limited IP-in-IPv6/GUEv6 exposure. A tunnel endpoint with a decapsulation IP must be configured. Check the full platform/configuration table rather than treating every EOS switch or newer release as affected or fixed.
Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.
Steps
What To Do Now
- Confirm. Inventory every Extensible Operating System asset and record its exact version, patch level, role, relevant configuration, and exposure.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Arista advisory.
- Remediate. Confirm the platform and configured tunnel endpoints, then apply advisory 0137's ACL mitigation and validate permitted and rejected traffic. Arista plans no software upgrade path or hotfix for this issue.
- Validate. Confirm the intended tunnel endpoints with
show interfaces vxlan 1, the relevant tunnel-interface output andshow ip decap-group. After mitigation, test expected forwarding and rejection of unexpected tunnel types, review counters and verify shared-IP services. These are proposed checks, not tests performed here. - Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.
Fixed Releases And Mitigation
Permanent Fix
Arista states that no software upgrade path is planned because of the risk to existing configurations, and no hotfix is available. The vendor resolution is the applicable ACL mitigation in advisory 0137. A newer EOS number is not evidence that this vulnerability is removed.
Workaround Or Temporary Mitigation
Use the advisory's upstream-filtering or on-device ACL approach for the exact platform and tunnel protocol. If the decapsulation IP also carries BGP, SSH or other legitimate traffic, permit those flows before a deny rule. On-device mitigation can require a disruptive TCAM profile change and feature tradeoffs; use Arista TAC where needed, and test forwarding and recovery before rollout.
Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.
Investigation And Recovery
CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.
When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.
Notes
Exploitation Evidence
Vendor statement: Arista reports exploitation of this vulnerability.
CISA statement: CVE-2026-7473 was added to KEV on 2026-06-09. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.
Validation And Boundaries
This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.
Related TechGeeks Resources
- TechGeeks Security Notice Center
- All Security Notices
- What to Do When a Device Hits CISA KEV
- Router CVE Exposure, Version, and Mitigation Checklist
- IoT Firmware Update and End-of-Support Checklist
- Live Protect and Runtime Vulnerability Shielding
References
Wrap-Up
Record whether CVE-2026-7473 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.
Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.
