CVE-2026-7473
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves network tunnel decapsulation on the switch, which is not related to HTTP traffic and thus cannot be filtered by a web application firewall.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-7473 being exploited?
Yes. CVE-2026-7473 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-7473?
CVE-2026-7473 is rated Medium with a CVSS score of 5.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-7473?
Yes. A fix has been recorded for CVE-2026-7473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-7473 affect?
CVE-2026-7473 affects arista:eos. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected4.36.0
- affected>= 4.35.0 and <= 4.35
- affected>= 4.34.0 and <= 4.34
- affected>= 4.33.0 and <= 4.33
- affected>= 4.32.0 and <= 4.32
- affected>= 4.31.0 and <= 4.31
- affected<= 4.30
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 10 Jun 2026 (SSVC 2.0.3).
timeline
- 5 Jun 2026Published
- 9 Jun 2026Added to CISA KEV (exploited in the wild) · 3 days later
- 10 Jun 2026First proof-of-concept repository on GitHub (unvetted) · 1 day later
- 10 Jun 2026CISA SSVC assessment: exploitation active · same day later
- 23 Jun 2026CISA remediation due date (US federal agencies) · 13 days later
- 7 Oct 2026CVE record last updated · 107 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 26 days later
- Advisoryarista.com /en/support/advisories-notices/security-advisory/22872-security-advisory-0137
- Advisoryarista.com /en/support/advisories-notices/security-advisory/24005-security-advisory-0137
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-7473
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.