Vendor scorecard
CISA lists 4 Arista vulnerabilities as exploited in the wild, 4 of them added in the last 12 months (up from 0 in the 12 months before). 0 (0%) are known to be used in ransomware campaigns. For entries added in the last two years, the median time from CVE publication to the KEV listing was 0 days. Most affected: VeloCloud Orchestrator (3), Extensible Operating System (1).
| Product | KEV entries |
|---|---|
| VeloCloud Orchestrator | 3 |
| Extensible Operating System | 1 |
| CVE | Vulnerability | Added |
|---|---|---|
| CVE-2026-114625 | Arista VeloCloud Orchestrator SQL Injection VulnerabilityVeloCloud Orchestrator | |
| CVE-2026-93952 | Arista VeloCloud Orchestrator Improper Input Validation VulnerabilityVeloCloud Orchestrator | |
| CVE-2026-16812 | Arista VeloCloud Orchestrator On-Prem OS Command Injection VulnerabilityVeloCloud Orchestrator | |
| CVE-2026-7473 | Arista Extensible Operating System Incomplete Comparison with Missing Factors VulnerabilityExtensible Operating System |
Get an email when CISA adds the next Arista CVE.
How to read this: CISA KEV lists vulnerabilities with reliable evidence of exploitation; a vendor with many entries is often one with a large, internet-facing install base, not necessarily worse engineering. "Publication → KEV" is the median number of days between the CVE's publication and its addition to KEV, for entries added in the last 24 months (4 entries); it is an upper bound on how long defenders had, since exploitation usually starts before the listing. Under NIS2 article 21(2)(d), supplier security is part of your risk management; this page is a starting point for that review. Compare vendors on the scorecard index.
We assess supplier security for NIS2 and DORA, from exploited-CVE history and patch response to contract clauses and evidence packs.
Get in touch →