Arista warns of actively exploited SQL injection in VeloCloud Orchestrator (CVE-2026-114625)

What happened

Arista has confirmed that attackers are actively exploiting a critical SQL injection flaw in VeloCloud Orchestrator (VCO), the management platform that provisions and monitors VeloCloud SD-WAN edges. Tracked as CVE-2026-114625 and scored 9.9 on the CVSS scale, the vulnerability was disclosed in Arista security advisory SA-0199 on 22 October.

The advisory names two source addresses seen in the attacks, 74.82.197[.]86 and 38.54.50[.]151, but does not say when exploitation started, which deployments were hit, or what the attackers did once inside.

How the injection escalates privileges

VeloCloud Orchestrator is a multi-tenant system: operators and partners create customer accounts, each partner can manage a group of customers, and access is role based. The lowest built-in role for customer users is Enterprise Read Only, a tier meant for viewing inventory, topology and reports.

According to Arista, the flaw sits in the orchestrator backend, where a SQL query is assembled from request data. Because the input becomes part of the statement rather than merely a value inside it, a crafted request can change what the query does. Arista describes the result as code running with the privileges of a local superuser — in effect the operator role, which has full access.

That landing point explains the severity score: an account designed for read-only visibility can carry out actions reserved for the operator tier.

What an attacker needs

Two conditions apply, and a writeup on dev.io... on dev.to summarising the advisory notes that both are routine in enterprise deployments. The attacker needs network access to the VCO web interface, which Arista states is exposed by default and cannot be switched off through an orchestrator setting, plus a valid login at Enterprise Read Only or above — including partner-held accounts that administer several customers.

This is the third VCO flaw Arista has reported as exploited since late July, but the first that requires authentication. The July issue, CVE-2026-16812, and the September issue, CVE-2026-93952, could be abused without any credentials at all, so the bar has risen only slightly.

Reach of a successful attack

An operator-level session on the orchestrator governs the SD-WAN fabric for every customer under that tenant. Arista also says the flaw may let an attacker affect the VCO host itself, with the ability to expose, modify or disrupt the orchestrator and the data it manages.

VeloCloud Edge and Gateway hardware do not carry the vulnerability, but the orchestrator is where configuration for those devices is written, making this a control-plane compromise rather than a device-level one.

Fixed releases

Fixes vary by release train: 5.2.3.18 and later for the 5.2 train, 6.1.3.10 and later for 6.1, and 6.4.2.12 and later for 6.4. Arista has already patched its Hosted and Dedicated orchestrators. The 7.0 train is not listed, and the advisory states that a release absent from the list is not vulnerable; end-of-support trains were not evaluated, and customers on them should contact Arista's Technical Assistance Center about upgrade paths.

One detail the writeup stresses: orchestrators running the builds that fixed the July and September flaws remain exposed, because those builds predate the current fixes. Patching once over the summer does not cover this.

Interim measures and compromise checks

Until a fixed release is installed, Arista recommends restricting the VCO web interface to trusted administrative networks, monitoring for connections from the two known malicious addresses, watching for unexpected outbound traffic from the VCO host, blocking outbound ports that normal operation does not need, hunting for backdoor daemons and webshells, and reviewing recent administrator activity for unexplained changes.

Admins should also block and search logs for the two addresses above, and inspect VCO web access logs for requests with unusual path components, encoded characters, references to internal services or abnormal request rates. If compromise is suspected, preserve web, application, system and database logs and relevant file timestamps before repairing anything.

The earlier advisories warned that a compromised orchestrator could open a path to edge devices; for this flaw Arista does not say whether that still holds, or whether upgrading evicts an attacker who already got in. An orchestrator that was reachable before the upgrade should still be treated as a system whose operator tier needs verifying.

For sizing, the dev.to writeup cites a ZoomEye query matching 529 VeloCloud-branded assets, while cautioning that this measures product exposure, not confirmed-vulnerable installations.

Why it matters

This is active exploitation of a control-plane system that many organisations treat as trusted infrastructure, and the entry requirement is deliberately low: any legitimate read-only credential, including partner accounts, is enough. With the web interface exposed by default and no supported way to disable that exposure from within VCO, network-level restriction becomes the practical interim defence. It is also the third exploited orchestrator flaw in roughly three months, a pattern that suggests sustained targeting of VeloCloud deployments rather than an isolated bug. Administrators who patched in July or September are not covered here and must upgrade again, and anyone running a previously internet-reachable orchestrator should assume the operator tier needs scrutiny, not just the patch.