CVE-2026-7473 is an incomplete comparison vulnerability in Arista Extensible Operating System (EOS) affecting supported platforms configured for tunnel decapsulation, including VXLAN, decap-groups, or GRE tunnel interfaces. The switch validates the destination IP against a configured decapsulation IP but does not verify the tunnel protocol type before decapsulating and forwarding traffic. As a result, a device configured to terminate one tunnel type can incorrectly accept, decapsulate, and forward packets encapsulated with other unexpected tunnel protocols, provided the outer destination IP matches the configured decapsulation endpoint. The issue is configuration-dependent rather than purely version-dependent and has been reported as exploited in the wild.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone Python proof-of-concept exploit for CVE-2026-7473 affecting Arista EOS tunnel decapsulation behavior. The repo contains three files: a MIT license, a README with vulnerability description/usage/mitigation guidance, and a single executable script, arista_tunnel_bypass.py, which is the main entry point. The Python script uses Scapy to craft raw network packets for multiple tunnel types. Based on the visible code and CLI flow, it supports generating GRE, VXLAN, and GUE packets directly, and the truncated portions strongly indicate additional support for IP-in-IP and NVGRE-related bypass tests. The exploit logic is centered on sending an unexpected tunnel protocol to a switch whose decapsulation IP matches the outer destination IP, attempting to trigger improper decapsulation and forwarding of the inner packet. This demonstrates the core vulnerability: missing tunnel protocol type verification on affected Arista EOS devices. Capabilities include: building randomized outer source IPs, targeting a user-supplied decapsulation IP, embedding simple inner payloads (UDP, Ethernet/IP, ICMP), and running several exploit modes such as vxlan-gre, gre-vxlan, gre-ipip, gue, nvgre, or all. The script also includes a check-config mode, but the README and code indicate scanning is not fully implemented and manual identification of vulnerable configuration is still required. Operationally, this is an active network exploit/validation tool rather than malware or a post-exploitation implant. It does not establish persistence or a shell; instead, it validates whether unexpected tunneled traffic is decapsulated and forwarded. Because it contains working packet-generation and exploit routines but only basic hardcoded payloads, the maturity is best classified as OPERATIONAL.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Arista EOS used here as an example of an actively exploited flaw that was slow to propagate into public CVE databases, has no vendor patch, and requires configuration-based ACL mitigations rather than version-based remediation.
A vulnerability in Arista EOS highlighted as an example of poor CVE propagation and remediation challenges; it was reported as exploited in the wild, affects essentially every release, and relies on configuration-based mitigations rather than a software patch.
An Arista Extensible Operating System vulnerability mentioned only in related content.
A configuration-dependent vulnerability in Arista EOS switches where tunnel decapsulation checks the destination address but not the tunnel protocol type, allowing improperly decapsulated traffic to be forwarded into internal network segments.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.