VulnerabilityPublished 5 Jun 2026Updated 7 Oct 2026

CVE-2026-7473: Arista Networks EOS · Incomplete Comparison with Missing Factors

Affects Arista Networks EOSSource CVE Database V5

Exploited in the wild · KEV due 23 Jun 2026 · 1% EPSS : apply the vendor's fix or mitigations to Arista Networks EOS now.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 23 Jun 2026 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 5 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 4 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Arista Networks, Inc.
29 Apr 202620:08 UTC, 37 days before disclosure
CVE published
on cve.org
5 Jun 202616:22 UTC, t = 0
In Threat Radar
record ingested
5 Jun 202616:48 UTC, 26 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
9 Jun 2026, 4 days after disclosure
KEV remediation due
US federal deadline
23 Jun 2026, 18 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Affected software

Product	Affected	Fixed in
Arista NetworksEOS	Affected >=4.35.0 <=4.35 >=4.34.0 <=4.34 >=4.33.0 <=4.33 >=4.32.0 <=4.32 >=4.31.0 <=4.31 <=4.30 =4.36.0	Fixed in–

Check the firmware or software version for Arista Networks EOS in the device's admin interface against the vendor advisory.

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.

Impact

The vulnerability allows an attacker to send unexpected tunneled packets to the switch that match the configured decapsulation IP but use a different tunnel protocol than configured. This may lead to the switch incorrectly processing and forwarding these packets, potentially causing unintended network behavior or information leakage. The integrity of the network traffic can be impacted, but confidentiality and availability impacts are not indicated. The scope of the vulnerability is changed, meaning it can affect resources beyond the initially vulnerable component.

Mitigation

Users should monitor the vendor advisory for updates and consider restricting tunnel decapsulation configurations or applying network-level controls to limit unexpected tunneled traffic until a fix is available.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Jun 2026, 09:16 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-1023

Technical details

References

Community reviews

Related threats