Skip to content
Threat Brief

← All advisories

CVE-2026-7473

Medium 6.9KEV · exploitedFix status unknown

Arista EOS Unexpected Tunnel Protocol Decapsulation and Forwarding Bypass

Record last updated

CVSS score

6.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

1.1%

Higher than 67% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

151days overdue

Passed 151 days ago for U.S. federal agencies

Description

On affected platforms running Arista EOS where a tunnel decapsulation configuration—such as VXLAN (Virtual Extensible LAN), decap-groups, or a GRE (Generic Routing Encapsulation) tunnel interface—is present, the switch will incorrectly decapsulate and forward other unexpected tunneled packet with a destination IP matching its configured decapsulation IP. This occurs because the switch does not verify the tunnel protocol type, potentially leading to the unexpected processing of non-configured tunnel traffic. This issue has been reported as being exploited in the wild.

Weakness: CWE-1023

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
There are two broad approaches to mitigate this issue - (1) applying ACLs on upstream devices or (2) applying ACLs on the devices where the unexpected decapsulation is happening. In both cases, the idea is to either selectively allow only legitimate tunnel traffic or to selectively block malicious tunnel traffic. For example, if a network is configured to forward VXLAN traffic, but GRE traffic is being unexpectedly forwarded, then ACLs can be used to either selectively allow just VXLAN traffic or selectively block GRE traffic. More details about using the ACL feature can be found in the Arista User Manual https://www.arista.com/en/um-eos/eos-acls-and-route-maps#xx1150869 . A note of caution, the following ACL-based mitigation recommendations assume that the tunnel IP is dedicated solely to receiving the configured tunnel protocol traffic. When adapting these rules for your environment, it is important to explicitly permit any additional protocol traffic—such as BGP or SSH—if that IP serves multiple functions. To maintain connectivity, ensure these permit statements are sequenced before any deny statements directed at the decapsulation IP. The following configurations align with the recommendations outlined in the Arista EOS Hardening Guide https://arista.my.site.com/AristaCommunity/s/article/arista-eos-hardening-guide#Comm_Kna_ka0Uw00000097VJIAY_71 . Source (opens in a new tab)
Vendor guidance
arista.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
AristaExtensible Operating SystemNot documentedNot documentedCISA KEV
Arista NetworksEOSfrom 4.31.0 up to and including 4.31Not documentedCVE Program
Arista NetworksEOSfrom 4.32.0 up to and including 4.32Not documentedCVE Program
Arista NetworksEOSfrom 4.33.0 up to and including 4.33Not documentedCVE Program
Arista NetworksEOSfrom 4.34.0 up to and including 4.34Not documentedCVE Program
Arista NetworksEOSfrom 4.35.0 up to and including 4.35Not documentedCVE Program
Arista NetworksEOS4.36.0Not documentedCVE Program
Arista NetworksEOSall versions up to and including 4.30Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Arista

    Source: CVE Program (opens in a new tab)

  2. 09 Jun 2026KEV

    Added to the CISA Known Exploited Vulnerabilities catalog

    Source: CISA KEV (opens in a new tab)

  3. 09 Jun 2026Exploitation

    Exploitation confirmed by CISA KEV

    Source: CISA KEV (opens in a new tab)

Vendor guidance and references