VeloCloud Orchestrator’s third exploited flaw since July makes each earlier fix obsolete
CVE-2026-114625 lets a read-only tenant account become a superuser operator on on-premises VeloCloud Orchestrator. It is the third exploited orchestrator flaw in three months, and each one has raised the minimum safe build.

On-premises VeloCloud Orchestrator now has three actively exploited vulnerabilities in three months. The newest, CVE-2026-114625, turns any valid portal login into control of the orchestrator [1]. The more important point for operators is that each fix has been overtaken by the next one. An orchestrator patched for July’s flaw, or for September’s, is still exploitable today [1][2][3].
VCO is the management plane for VeloCloud SD-WAN. It configures and monitors edge devices across an estate [5][12]. Compromise of the orchestrator is therefore compromise of the network’s control point, not of one appliance. Arista has said so directly: a VCO compromise may also give attackers access to VeloCloud Edge devices [2][3].
What the advisories say
Arista published Security Advisory 0199 on 22 October 2026 [1][14]. It describes CVE-2026-114625 as an SQL injection (CWE-89) with a CVSS v3.1 score of 9.9 and a CVSS v4.0 score of 9.4 [1]. Reporting has used both figures: SOCRadar and InfoSec Today cite 9.9, while Security Affairs cites 9.4 [8][9][13]. Both are Arista’s scores under different CVSS versions.
The advisory states that any authenticated user can gain operator privileges and masquerade as a local superuser operator [1]. The minimum role needed is Enterprise Read Only, the lowest built-in tenant role [1]. The attacker also needs network access to the VCO web interface. Arista says VCO is exposed by default and that no configuration prevents this [1]. The company states that it detected the issue itself and that it is known to be actively exploited [1]. Hosted and Dedicated VCO instances were affected and have already been patched [1]. VeloCloud Gateway and Edge are not affected [1][8].
Arista has not named an attacker, a victim count or a start date for the activity [8][9]. It published two source addresses seen in the attacks [1][5]. InfoSec Today reports that both geolocate to Japan [13]. Arista’s advisory does not state a location, and geolocation is not attribution. R3KONX does not reproduce the addresses here; they are in the vendor advisory.
CISA added the flaw to its Known Exploited Vulnerabilities catalog on 23 October. Security Affairs and InfoSec Today report a remediation deadline of 26 October for US federal civilian agencies [9][13].
Three flaws, three rising floors
The first flaw, CVE-2026-16812, was published in Advisory 0144 on 27 July 2026. It was an OS command injection with a CVSS score of 10.0 and needed no credentials [3]. Fixed builds were 5.2.3.14, 6.1.3.4 and 6.4.2.4, and 7.0.0.1 for the 7.0 train [3][12]. CISA listed it the same day [11]. The Cloud Security Alliance gives a 30 July federal deadline [11]. Security Affairs gave 20 July, a date before the listing itself and probably an error [10].
The second, CVE-2026-93952, followed in Advisory 0183 on 22 September. Arista classed it as improper input validation (CWE-20), scored 10.0 under CVSS v3.1 [2]. It needed no credentials either. It applied only where certificate-based authentication from Edge to VCO was configured, and the attacker needed the public part of an Edge certificate [2][7]. Arista listed file, service and web-server header indicators for that campaign [2][7]. CISA listed it the same day, with a 25 September deadline [6]. At release, fixes existed only for the 5.2 and 6.4 trains [2][7].
The pattern matters more than any single CVE. The September affected range included the builds that fixed July’s flaw [7]. The October thresholds of 5.2.3.18, 6.1.3.10 and 6.4.2.12 sit above both earlier fixes [1][8]. SOCRadar makes the same point: earlier VCO fixes fall below the new thresholds [8]. A team that closed the July ticket and the September ticket is still running a vulnerable orchestrator.
Advisory 0199 lists affected and fixed versions only for the 5.2, 6.1 and 6.4 trains [1]. Both earlier advisories also covered 7.0 [2][3]. The October advisory does not explain the omission. Operators on 7.0 should confirm their status with Arista TAC rather than assume they are unaffected.
Arista has now patched four exploited zero-days this year. BleepingComputer lists CVE-2026-7473 in EOS in May alongside the three VCO flaws [5][6].
What it means
The attack-surface requirement has moved. The July flaw needed only network reach [3]. The October flaw needs a login, but the weakest one will do [1]. In multi-tenant and partner-managed deployments, read-only accounts are often issued widely and reviewed rarely. A phished or reused read-only credential is now a route to full orchestrator control.
Orchestrator compromise also has downstream consequences. Arista’s September advisory, 0182, describes CVE-2026-86109 in VeloCloud Edge [4]. The Edge update workflow may accept update bundles without proper signature validation [4]. Arista found it internally and reports no known exploitation [4]. Its preconditions include the ability to upload packages to VCO, and Arista names VCO compromise as one path [4]. An attacker with superuser operator access on an orchestrator is close to that position. That is a reason to treat Edge integrity as in scope during any VCO investigation.
What to do
- Inventory every on-premises VCO and record its exact build. Compare it with Advisory 0199, not with whichever advisory last triggered a patch [1].
- Upgrade to 5.2.3.18, 6.1.3.10 or 6.4.2.12 or later on the matching train [1]. Contact Arista TAC for 7.0 and for end-of-support trains, which Arista did not assess [1].
- Restrict the VCO web interface to trusted administrative networks. Arista presents this as risk reduction, not a fix [1][2].
- Audit tenant, partner and customer accounts, especially Enterprise Read Only. Disable stale access [8]. Enforce strong authentication on the accounts that remain.
- Before remediating a suspected compromise, preserve web access, application, system and database logs and file-system timestamps [1][2].
- Hunt across all three campaigns, not only the newest. Review web access logs for unusual URL-like paths, encoded characters, references to internal services and high request rates. Check for unexpected outbound traffic, unexplained administrator changes, backdoor daemons and web shells, using the indicators in Advisories 0144, 0183 and 0199 [1][2][3].
- If compromise is found, rotate credentials and API tokens, review administrator activity, validate managed Edge state and rebuild the orchestrator from trusted sources [2][3][11].
- Review VCO audit history for unexpected Edge update operations or version changes, and bring Edges to the builds fixed in Advisory 0182 [4].
- Move management planes behind dedicated management networks, jump hosts and allowlisting. New York State ITS rated the July flaw high risk for large and medium government entities and businesses [11][12].
The offensive security view
Exposed, centrally privileged management planes keep attracting exploit development. VCO is now a repeat target, with three distinct bug classes in one quarter: command injection, input validation and SQL injection [1][2][3]. Vulnerability management that tracks closed CVE tickets, not current minimum builds, will keep missing this. Treat the orchestrator as a tier-zero asset, review it against the latest advisory every time one is published, and expect the next disclosure to raise the floor again.
Sources
Every R3KONX article cites its primary material. 14 sources, in order of first citation. Links open the original publication.
- Security Advisory 0199 (CVE-2026-114625, VeloCloud Orchestrator On-Prem) Arista Networks · 2026-10-22
- Security Advisory 0183 (CVE-2026-93952, VeloCloud Orchestrator On-Prem) Arista Networks · 2026-09-22
- Security Advisory 0144 (CVE-2026-16812, VeloCloud Orchestrator) Arista Networks · 2026-07-27
- Security Advisory 0182 (CVE-2026-86109, VeloCloud Edge update signature validation) Arista Networks · 2026-09-09
- Arista patches new VeloCloud Orchestrator zero-day exploited in attacks BleepingComputer · 2026-10-22
- Arista patches actively exploited VeloCloud Orchestrator zero-day BleepingComputer · 2026-09-23
- New CVSS 10.0 VeloCloud Orchestrator flaw actively exploited in certificate-based setups The Hacker News · 2026-09-22
- CVE-2026-114625: VeloCloud Orchestrator flaw exploited SOCRadar · 2026-10-23
- U.S. CISA adds Arista VeloCloud Orchestrator flaw to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-10-24
- U.S. CISA adds Arista VeloCloud Orchestrator and Fortinet FortiOS flaws to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-07-28
- Arista VeloCloud zero-day: same-day KEV signals new patch reality Cloud Security Alliance · 2026-07-29
- A vulnerability in VeloCloud Orchestrator (VCO) On-Prem could allow for remote code execution (Advisory 2026-072) New York State Office of Information Technology Services · 2026-07-28
- CISA flags two actively exploited critical flaws in Collabora Online and Arista VeloCloud InfoSec Today · 2026-10-24
- Security Advisories (listing) Arista Networks · 2026-10-23
Researched and written by the R3KONX analysis desk from the cited primary material. Exploitation status, affected versions and indicators come from Arista's own advisories; no source reviewed names a threat actor, gives victim counts or gives internet-exposure figures, and no source reviewed mentions Malaysia. Corrections to event@r3konx.asia.
