Overview
Arista has warned customers that attackers are actively exploiting a critical SQL injection vulnerability in the VeloCloud Orchestrator (VCO), the central management platform used to administer VeloCloud SD-WAN environments. Tracked as CVE-2026-114625 and rated 9.9, the vulnerability is particularly concerning because exploitation requires only network access to the VCO web interface and a valid account. Even the lowest built-in customer role, Enterprise Read Only, can reportedly be used to escalate privileges to the highest level of control. The incident demonstrates a fundamental security principle for modern networks: low-privilege access to a management platform can become high-privilege access to the infrastructure behind it.
Read-Only Does Not Always Mean Low Risk
The vulnerability does not require an administrator account. An attacker with a valid Enterprise Read Only account can reportedly exploit the SQL injection flaw and gain operator-level privileges, effectively crossing the boundary between viewing the environment and controlling it. That makes this vulnerability particularly important in environments where customer, partner and operator accounts coexist within the same orchestration platform. A read-only identity should not provide a realistic pathway towards complete management control. When it does, the distinction between account privilege levels becomes largely theoretical.
The Management Plane Is the Real Target
VCO is not simply another application running alongside the network. It is the central management system for VeloCloud SD-WAN environments, providing the platform through which customers, partners and network infrastructure are managed. Compromise of the orchestrator can therefore have consequences beyond the VCO host itself. An attacker who gains operator-level access may be able to manipulate the orchestrator, access sensitive management information or potentially influence the infrastructure it controls. This is why management systems deserve a higher security classification than ordinary application servers. Compromising the control plane can be more valuable than compromising an individual endpoint.
Authentication Is Only One Layer
The vulnerability also highlights an important distinction between authentication and authorisation. Authentication establishes that an account is permitted to access the platform. Authorisation determines what that account should be allowed to do. In this case, a legitimate low-privilege account can reportedly be used to cross the authorisation boundary through the vulnerability. Strong passwords and multifactor authentication remain important, but they cannot compensate for a vulnerability that allows an already authenticated user to escalate privileges. Security architecture therefore needs multiple layers: strong identity controls, application security, network restrictions and monitoring of privileged activity.
The Third Exploited VCO Vulnerability
CVE-2026-114625 is reportedly the third VCO vulnerability exploited in attacks since July 2026. The July and September vulnerabilities did not require authentication, while the latest flaw does. However, previous security releases do not automatically protect against the new vulnerability. This is an important operational lesson. Installing a previous security update can remove one attack path while leaving another vulnerability in the same management platform exploitable. Security teams therefore need to assess the current security state of the platform, rather than assuming that a recent upgrade means the system is fully protected.
Restrict the Orchestrator While Preparing the Upgrade
For on-premises deployments, Arista has released fixes for the affected release trains:
- VCO 5.2 → 5.2.3.18 or later
- VCO 6.1 → 6.1.3.10 or later
- VCO 6.4 → 6.4.2.12 or later
Hosted and Dedicated Orchestrators have already been patched.
Where an immediate upgrade is not possible, access to the VCO web interface should be restricted to trusted administrative networks. Unnecessary outbound connectivity should also be limited, while administrator activity and unexpected system behaviour should be monitored.
These measures reduce exposure but do not remove the vulnerability.
Patching Does Not Answer the Compromise Question
Because exploitation is already occurring, upgrading the VCO should not automatically be considered the end of the incident. Organisations need to determine whether their orchestrators were accessed before remediation. Administrator activity, web access logs, system activity and unexpected configuration changes should be reviewed. This is particularly important because the advisory does not establish what attackers did after successfully exploiting the vulnerability.
The unanswered question is therefore not simply “Has the VCO been patched?”
It is “Was the management plane already compromised before it was patched?”
Expert in the Cloud Insight
The VeloCloud vulnerability demonstrates why management infrastructure needs to be treated as a security boundary in its own right. A compromised workstation may affect one user. A compromised orchestrator can potentially provide a pathway towards an entire managed network environment. The combination of a valid low-privilege account, an internet-accessible management interface and a privilege-escalation vulnerability creates a particularly dangerous trust relationship. In network architecture, the control plane should never be treated as just another application — because whoever controls the control plane may ultimately control the network.
Leave a Reply