As reported by The Hacker News on October 22, 2026, Arista has disclosed a critical SQL injection zero-day in its VeloCloud Orchestrator (VCO) that is being actively exploited. For Shield53, the most important detail isn't the CVSS 9.9 score—it's that this is now the third exploited VCO flaw disclosed since July, and the first that weaponizes a valid (low-privilege) session to reach the top of the management plane.
Why This Matters More Than the Score Suggests
VCO is the brain of a VeloCloud SD-WAN fabric. Whoever controls the orchestrator controls edge provisioning, tunnel policies, routing, and customer tenancy across potentially thousands of branch sites. A privilege escalation from Enterprise Read Only to operator—and reportedly to local superuser on the VCO host—collapses the entire tenant isolation model that partners and managed-service providers rely on. One compromised low-trust account becomes a network-wide compromise.
The arithmetic of SD-WAN risk is brutal: a single orchestrator is a force multiplier. Defenders should treat VCO exposure like they treat domain controllers—internally trusted, externally catastrophic if leaked.
Two things make this disclosure particularly uncomfortable for defenders:
- VCO is exposed by default, and no configuration toggle prevents it. That means every on-prem deployment that hasn't been segmented behind a VPN or zero-trust proxy is effectively internet-facing from an attacker's perspective.
- Fixes for July and September's flaws do not cover this one. Customers who patched to the September releases are still vulnerable. Patching fatigue is now a direct contributor to exposure.
Vulnerability Details
| Field | Value |
|---|---|
| CVE | CVE-2026-114625 |
| CVSS | 9.9 (Critical) |
| Type | SQL Injection / Privilege Escalation |
| Vendor / Product | Arista / VeloCloud Orchestrator (formerly VMware SD-WAN by VeloCloud) |
| Authentication | Required (any valid login, minimum role Enterprise Read Only) |
| Affected trains | 5.2 (before 5.2.3.18), 6.1 (before 6.1.3.10), 6.4 (before 6.4.2.12) |
| Not affected | 7.0 train, VeloCloud Gateway, VeloCloud Edge, Hosted & Dedicated Orchestrators (already patched) |
| Patch | Available — VCO 5.2.3.18, 6.1.3.10, 6.4.2.12 |
| Active exploitation | Yes — in the wild as of disclosure |
Who Is Most Exposed
Shield53 Recommendations
- Patch immediately to VCO 5.2.3.18, 6.1.3.10, or 6.4.2.12 depending on your release train. If you are on an unsupported train, engage Arista TAC for an upgrade path—do not assume end-of-support releases are safe.
- Remove VCO from internet exposure. Place the orchestrator behind a VPN, jump host, or reverse proxy with mTLS. There is no native VCO setting that does this for you.
- Audit and minimize low-privilege accounts. Revoke dormant Enterprise Read Only and partner accounts. Every one of them is now a known path to operator.
- Hunt for prior abuse. Review VCO audit logs for unexpected role changes, new operator accounts, configuration exports, or API token issuance originating from non-administrator sessions.
- Re-evaluate the SD-WAN management plane as a whole. Three exploited flaws in 90 days—two unauthenticated, one low-privilege—suggests the VCO attack surface deserves the same hardening and monitoring investment as identity providers and domain controllers, not the "appliance" tier it's often treated as.
The Broadcom-to-Arista transition was always going to surface legacy technical debt. What defenders should take from this week's advisory is that the debt is now being collected by attackers—and that "we patched last month" is no longer a sufficient answer for any VCO deployment.
