Arista patches another exploited VeloCloud Orchestrator zero-day, its third in four months
Another week, another network box under attack. Arista Networks on Thursday, Oct 22 patched CVE-2026-114625, a critical SQL injection flaw (CVSS 9.9) in its VeloCloud Orchestrator (VCO) management tool, and says it is already being exploited (SecurityWeek).
What the bug does
On an affected on-prem VCO, any logged-in user, even one with the lowest built-in tenant role, can gain operator privileges and act as a local “superuser operator.” That opens functions meant for internal use only. Arista found the issue itself and says VCO is exposed by default, with no configuration that blocks it.
What to do
- Update on-prem VCO to 5.2.3.18, 6.1.3.10 or 6.4.2.12. Every earlier release is affected. Arista has already patched hosted VCO.
- Until you can patch, restrict access to the VCO web interface, review recent admin activity and watch for webshells or backdoor processes.
- Arista saw attacks from two IP addresses, 74.82.197.86 and 38.54.50.151. Block them and search your logs for them.
- If you suspect a compromise, preserve VCO web, application, system and database logs before you fix anything.
Why it matters
It’s the third exploited VCO zero-day Arista has patched in four months, after CVE-2026-16812 in July and CVE-2026-93952 in September. VCO manages SD-WAN networks for businesses, so whoever gets in sits close to the network itself.
Koffee take: if your company runs VeloCloud on-prem, send this to IT today. Three in four months means attackers are watching this product closely.
Filed Oct 23, 2026 ~12:30 PM CT — Midday pass. Sources: SecurityWeek — Attackers Exploit Third Arista VCO Zero-Day in Four Months (Oct 23, 2026), citing Arista’s security advisory.