Skip to main content
Mallory
MediumCISA KEVExploited in the wildPublic exploit

Arista EOS tunnel decapsulation protocol verification flaw

IdentifiersCVE-2026-7473CWE-1023· Incomplete Comparison with Missing…

CVE-2026-7473 affects Arista Extensible Operating System (EOS) on affected platforms when tunnel decapsulation is configured, including VXLAN VTEPs, decap-groups, or GRE tunnel interfaces. The flaw causes the switch to incorrectly decapsulate and forward unexpected tunneled packets whose destination IP matches the device's configured decapsulation IP. The root cause is that EOS does not verify the tunnel protocol type before decapsulation, so a device configured to decapsulate one tunnel type can also accept and process other non-configured tunnel protocols sent to the same decapsulation IP. Arista has reported that the issue has been exploited in the wild.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to inject unexpected tunneled traffic that the switch will decapsulate and forward into internal network segments, despite that tunnel protocol not being configured for that endpoint. This can result in unintended packet processing, bypass of expected tunnel-type restrictions, and unauthorized reachability into networks behind the decapsulation device. The primary impact is improper forwarding of attacker-supplied traffic across trust boundaries rather than direct code execution on the switch.

Mitigation

If you can’t patch tonight, do this now.

Mitigate by filtering traffic to the decapsulation IP so that only legitimate tunnel traffic is permitted. Arista recommends applying ACLs either on upstream devices before the traffic reaches the tunnel endpoint or directly on the decapsulation switch. Filters should selectively allow only expected tunnel protocols and, where applicable, expected UDP ports, or block non-authorized tunnel traffic destined for the decapsulation IP. On some hardware families, implementing mitigation on the decapsulation switch requires TCAM profile changes and platform-specific ACL mechanisms such as MAC ACLs with User Defined Fields or IPv6 PACLs.

Remediation

Patch, then assume compromise.

Arista states that no software upgrade path or hotfix is planned for CVE-2026-7473 because a protocol-verification fix could break existing deployments. Customers should follow Arista's published mitigation guidance and contact Arista TAC if assistance is required. Where organizational policy requires KEV remediation, apply vendor-recommended mitigations immediately and validate that only intended tunnel traffic can reach decapsulation IPs.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Arista NetworksEosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.