A partner can manage many customers: why VeloCloud tenant structure raises the stakes of CVE-2026-114625

Arista's description of VeloCloud Orchestrator includes a sentence that shapes the blast radius of CVE-2026-114625: operators create customer and partner accounts, and each partner can manage a group of customers.

A partner login is a normal business arrangement in managed SD-WAN. It is also, under this flaw, a route to operator rights that reach every customer in that partner's group.

The privilege structure

VCO separates roles. Operators sit at the top. Partners administer sets of customers. Customer users get roles such as Enterprise Read Only, the lowest built-in role for customer accounts.

CVE-2026-114625 is a SQL injection that lets anyone who can log in to the orchestrator, even with that read-only customer account, gain operator privileges. Arista rates it 9.9 and states it is being exploited.

For a service provider, the question is whether any account with interface access, across every tenant and partner relationship, can be turned into an operator session.

Why authentication does not narrow this much

The advisory's prerequisites are network access to the VCO web interface and a valid login at Enterprise Read Only or higher. VCO is exposed by default, and no setting removes that exposure.

Read-only accounts are common in multi-tenant operations. They support reporting, compliance review and monitoring. Partner staff who oversee several customers need visibility across those customers. Each of those accounts meets the login requirement.

The two earlier VCO vulnerabilities, CVE-2026-16812 and CVE-2026-93952, required no login. Both were exploited. CVE-2026-114625 is the first of the three that requires one, and it still scores near the maximum.

Impact in a partner-managed estate

Operator privileges on VCO mean control over the SD-WAN configuration for every customer that tenant manages. Arista also says the flaw may let an attacker affect the VCO host itself and expose, modify or disrupt the orchestrator and its data.

The advisory does not describe which orchestrators were attacked or what happened afterwards. What it does provide is a way to check: two source addresses, 74.82.197[.]86 and 38.54.50[.]151, and log patterns to search for.

Patch requirements per tenant

Train	Fixed release
5.2	5.2.3.18
6.1	6.1.3.10
6.4	6.4.2.12

Hosted and Dedicated orchestrators were patched by Arista, so those tenants do not perform the upgrade themselves. Self-managed deployments need the fixed build for their train. VeloCloud Gateway and VeloCloud Edge are not affected. The 7.0 train is unlisted and, per Arista, not vulnerable.

Builds that closed the July and September flaws are older than these fixes and remain exposed. Any tenant whose last maintenance window was in the summer should be rechecked.

Operational steps for providers

A provider managing several customers can act on these without waiting for a full patch cycle:

Enumerate every account with web interface access and its role, including read-only and partner accounts.
Restrict VCO web interface reachability to trusted administrative networks, as Arista recommends.
Monitor for connections from the two addresses named in the advisory.
Watch the VCO host for unexpected outbound traffic and check for backdoor daemons and webshells.
Review recent administrator activity for changes no one has claimed.

After the patch

The advisory does not say whether upgrading removes access already obtained, or whether a compromised orchestrator still exposes edge devices. Providers carrying customers on the same orchestrator should treat those as open items and preserve logs before remediation, as Arista advises.

Exposure

A ZoomEye search for title="VeloCloud" returns 529 matching assets. That describes how much VeloCloud web surface is visible publicly, not how many orchestrators are vulnerable.