A tenant with read-only access to an affected on-premises Arista VeloCloud Orchestrator can gain operator privileges through a SQL-injection flaw. CISA added CVE-2026-114625 to its known-exploited catalog on October 23 and set an October 26 action date for federal agencies. For teams running their own VCO, an authenticated low-privilege tenant with network access to the web interface can reach privileged orchestration functions.
Arista’s published CVE record says an affected user can masquerade as a local “superuser operator” and reach functionality intended for internal use. That reach may compromise the VCO host and the confidentiality, integrity, and availability of the orchestrator and its managed data. Arista says hosted and Dedicated VCO instances were affected and have already been patched.
A reader session reaches operator functions
The weakness is SQL injection (CWE-89) in the on-prem orchestrator. Arista describes the access path as a route to the VCO web interface plus a valid authenticated portal session; Enterprise Read Only, its lowest built-in tenant role, meets the role requirement. An ordinary tenant login can therefore become a path to privileged local operator functions. Arista says VCO is exposed by default and “There is no configuration that can prevent the exposure.” Restricting reachability reduces who can try the path while the software is being upgraded.
This differs from Nulltap’s earlier reports on certificate-based Edge authentication and unauthenticated command injection. Their access requirements and fixed builds belong to different CVEs. Track this SQL-injection issue under CVE-2026-114625 rather than carrying over those release checks.
Match the installed release train
Arista identifies affected on-prem builds from 5.2.0 up to but excluding 5.2.3.18, from 6.1.0 up to but excluding 6.1.3.10, and from 6.4.0 up to but excluding 6.4.2.12. The respective first fixed releases are 5.2.3.18, 6.1.3.10, and 6.4.2.12; use a fixed release in your active train. The CVE record classifies other versions as unaffected by default, so verify the actual deployed build and train rather than matching only a product name.
Inventory on-prem VCO instances, record their installed build, and determine which networks and tenant accounts can reach the web interface. Put that interface behind trusted administrative-network access while scheduling the upgrade. Arista calls those restrictions defense in depth, not a substitute for installing a fixed release. After upgrading, confirm the running build and test that a host on an untrusted segment cannot load the portal while the approved administration path still works.
Review the orchestrator after exposure
For a vulnerable VCO reachable by tenant users or less-trusted networks, review recent administrator changes and portal access alongside unexpected outbound traffic from the VCO host. Arista also advises looking for backdoor daemons and webshells and considering blocks on outbound ports the host does not need. Unexpected operator activity from a tenant account deserves investigation even if the account’s login itself was legitimate; ordinary authentication alone is a poor filter for this privilege path.
CISA’s exploited listing calls for forensic triage. Preserve available portal, administrator and host activity as you investigate suspicious changes, and handle any compromise separately from the version upgrade. Confirm the fixed running build and the restricted portal path on every on-prem instance; those two checks address the software flaw and the reachability that makes a low-privilege session dangerous.