Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify EOS switch with VXLAN/GRE decap configured
-
DeliveryDetermine decapsulation destination IP
-
ExploitCraft tunneled packet with non-configured protocol type
-
InstallSend packet to decap IP over network
-
C2Switch matches IP, skips protocol-type verification
-
ExecuteSwitch decapsulates and forwards inner payload
-
ImpactInjected traffic enters protected network segment
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation is only possible when the target Arista EOS switch has an active tunnel decapsulation configuration - specifically at least one of: a VXLAN VTEP/decapsulation IP, a decap-group configuration, or a GRE tunnel interface. Switches without any of these configurations are not affected. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms no authentication is required, no additional attack requirements apply, and no user interaction is needed once the network condition is met. The primary limiting factor is the mandatory presence of a tunnel decapsulation configuration: production datacenter switches running EVPN/VXLAN fabrics, GRE-based WAN overlays, or decap-group policies are at risk, while purely L2/L3 forwarding-only deployments without overlay configs are not. Network reachability to the decapsulation IP address is also required - switches where decap IPs are reachable only from trusted internal segments have a reduced exposure surface. |
| Impact | The CVSS 4.0 base score of 6.9 with vector AV:N/AC:L/AT:N/PR:N/UI:N reflects unauthenticated, low-complexity, remotely triggerable exploitation with no user interaction needed - a favorable attack surface. However, impact is constrained: VC:N/VA:N/SC:N/SA:N, with only low integrity impact on both vulnerable and subsequent systems (VI:L/SI:L). The Exploit Maturity field (E:X) is marked 'Not Defined' in the submitted CVSS vector, which is in tension with the description's statement that the issue has been reported exploited in the wild - this discrepancy should be verified against the Arista advisory. EPSS data was not provided; the absence of a confirmed CISA KEV entry means automated, widespread scanning cannot be confirmed. Despite the moderate score, real-world risk is elevated for environments relying on VXLAN or GRE-based segmentation (multi-tenant datacenters, SD-WAN fabrics, EVPN deployments) because the vulnerability can silently bypass network boundaries. The combination of network reachability, no authentication requirement, and a reported in-the-wild status makes this a genuine operational priority for affected infrastructure despite the 'low integrity' CVSS impact rating. |
| Exploit ScenarioDerived | An attacker on the internet or an adjacent network crafts tunneled IP packets (for example, VXLAN-encapsulated frames) addressed to a GRE-configured EOS switch's decapsulation IP. The switch, checking only the destination IP and not the protocol type, decapsulates the VXLAN frames and forwards the inner traffic into the protected network segment as if it originated from a trusted tunnel peer. This allows the attacker to inject arbitrary frames into a VLAN or tenant segment that would otherwise be inaccessible, potentially facilitating lateral movement or spoofing within that segment. No public proof-of-concept code was referenced in the provided data, but the described exploitation is low complexity given the AV:N/AC:L/PR:N CVSS profile. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 05, 2026
Tunnel decapsulation logic in Arista EOS fails to verify the encapsulation protocol type, allowing any tunneled packet destined for a configured decapsulation IP to be silently unwrapped and forwarded into the network. Unauthenticated remote attackers (PR:N, AV:N per CVSS 4.0) can inject traffic into network segments by exploiting this check bypass on switches with VXLAN, decap-groups, or GRE configurations. The CVE description explicitly states this issue has been reported as exploited in the wild; however, a CISA KEV entry was not confirmed in the provided data. The integrity impact is assessed as low on both the vulnerable and subsequent systems per CVSS 4.0 (VI:L/SI:L), but the network trust boundary violation in a core switching context warrants elevated operational priority.
RemediationAI
The primary remediation is to apply the vendor-released patch per Arista Security Advisory 0137, available at https://www.arista.com/en/support/advisories-notices/security-advisory/22872-security-advisory-0137. An exact fixed EOS version was not present in the provided data and must be confirmed from that advisory before upgrading. As a compensating control where immediate patching is not feasible, restrict which source IPs can send tunneled traffic to decapsulation endpoints using ACLs or firewall rules at the network perimeter, limiting exposure to trusted tunnel peers only - note this adds operational overhead and may not block insider threats. Additionally, if decap-groups or GRE tunnel interfaces are not actively required, temporarily removing the tunnel decapsulation configuration eliminates the vulnerable code path entirely but will disrupt overlay networking services. Operators should audit which tunnel protocols are legitimately in use and enforce protocol-specific ACLs as an interim control until patching is complete.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Arista EOS (cpe:2.3:a:arista_networks:eos:*:*:*:*:*:*:*:*) is the network operating system powering Arista datacenter and campus switches. The affected code path handles tunnel decapsulation for overlay protocols: VXLAN (UDP-encapsulated L2 frames over IP, typically port 4789), GRE (IP-in-IP generic encapsulation, protocol 47), and custom decap-groups. CWE-1023 (Incomplete Comparison with Missing Factors) is the root cause: the switch evaluates whether the destination IP matches a configured decapsulation endpoint but omits validating the encapsulation protocol field. This means a GRE-configured switch will also decapsulate VXLAN or arbitrary IP-in-IP traffic arriving at the same IP, violating the expected protocol boundary. In overlay network designs, tunnel endpoints are trusted demarcation points - bypassing protocol-type enforcement undermines network segmentation and tenant isolation.
Know when Eos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
Primary rating from Vendor (Arista) · only source for this CVE.
CVSS VectorVendor: Arista
Lifecycle Timeline
2DescriptionCVE.org
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.
Articles & Coverage 1
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of
Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execut
Remote code execution in OpenSSH's sshd server (regression of CVE-2006-5051) allows unauthenticated remote attackers to
Command injection in Arista EOS-based products lets an authenticated user of the gRPC Network Security Interface (gNSI)
The C+ mode offload emulation in the RTL8139 network card device model in QEMU, as used in Xen 4.5.x and earlier, allows
On affected modular platforms running Arista EOS equipped with both redundant supervisor modules and having the redundan
Heap-based buffer overflow in the PCNET controller in QEMU allows remote attackers to execute arbitrary code by sending
Arista EOS before 4.11.12, 4.12 before 4.12.11, 4.13 before 4.13.14M, 4.14 before 4.14.5FX.5, and 4.15 before 4.15.0FX1.
On affected platforms running Arista EOS with mirroring to multiple destinations configured, an internal system error ma
On affected platforms running Arista EOS with SNMP configured, a specially crafted packet can cause a memory leak in the
EOS v2.1.0 was discovered to contain a heap-buffer-overflow via the function txn_test_gen_plugin. Rated high severity (C
EUVD-2026-34858
GHSA-mcx4-vm6v-r473
NVD
CVE.org
CISA KEV
EPSS
Vulnrichment
VulDB
Exploit-DB