Skip to main content
All incident reports
Incident report

Third VeloCloud Orchestrator zero-day in four months exploited through SQL injection

Arista has fixed an actively exploited SQL injection flaw in on-premises VeloCloud Orchestrator, the management portal for its SD-WAN product. Any logged-in user, including one holding the lowest customer role, could take full operator control of the orchestrator.

· First published

The short version

  • The flaw. Arista published an advisory on 22 October for CVE-2026-114625, a SQL injection flaw rated 9.9 in on-premises VeloCloud Orchestrator (VCO). Arista says it found the issue itself and that it is being actively exploited.
  • Who can exploit it. An attacker needs network access to the VCO web interface and a valid login, with the lowest built-in customer role (Enterprise Read Only) sufficient. Arista says a successful attack lets that user act as a local superuser with access to internal-only functionality and can affect the orchestrator host and the data it manages.
  • Fixes and scope. Hosted and dedicated orchestrators are already patched; on-premises installations need the fixed build for their release train, such as 6.4.2.12 on the 6.4 train. VeloCloud Gateway and VeloCloud Edge are not affected.
  • Attack indicators. Arista names two IP addresses seen in the attacks, 74.82.197.86 and 38.54.50.151, and asks administrators to block them, check VCO logs and preserve evidence before remediating.
  • The pattern. This is the third exploited VCO zero-day Arista has patched since July, and the first of the three that requires a login. Arista has not said who is behind the attacks or which orchestrators were hit.

Timeline

DateEvent
May 2026Arista patches CVE-2026-7473, one of several exploited zero-days it fixed this year across its Extensible Operating System (EOS) and on-premises VCO.
July 2026Arista patches exploited VCO flaw CVE-2026-16812, which did not require authentication.
September 2026Arista patches exploited VCO flaw CVE-2026-93952, which did not require authentication.
22 October 2026Arista publishes an advisory and fixes for CVE-2026-114625, saying the flaw is known to be actively exploited.

The flaw and how it is exploited

CVE-2026-114625 is a SQL injection flaw, meaning crafted input lets an attacker manipulate the orchestrator's database, in VeloCloud Orchestrator. VCO is the web portal administrators use to configure and monitor a software-defined wide area network (SD-WAN) and its edge devices. Arista rates the flaw 9.9 out of 10.

Exploitation requires network access to the VCO web interface and a valid authenticated session. The minimum role needed is Enterprise Read Only, the lowest built-in role for customer users. Arista says any authenticated user can gain operator privileges and masquerade as a local superuser operator, reaching functionality meant for internal use only.

Arista says VCO is exposed by default, stating: "There is no configuration that can prevent the exposure." The company says it detected the issue and that it is known to be actively exploited, with attacks traced to two IP addresses.

Who is affected and what is fixed

On-premises VCO deployments on the 5.2, 6.1 and 6.4 release trains are affected until updated; each train has its own fixed build, with 6.4.2.12 covering the 6.4 train. Arista says hosted and dedicated orchestrators have already been patched. VeloCloud Gateway and VeloCloud Edge are not affected, and Arista says releases not on its list, including the 7.0 train, are not vulnerable.

Arista has not checked releases that have reached end of support; customers on an unsupported train are told to contact its Technical Assistance Center about upgrades. The advisory does not say whether 6.1.3.10, the fix for this flaw on the 6.1 train, also fixes September's CVE-2026-93952, which had no fixed 6.1 release listed.

Arista does not say when exploitation began, which orchestrators were hit, or what attackers did once inside. It advises restricting VCO web interface access to administrative networks, watching for unexpected outbound traffic, looking for backdoor daemons and webshells, and reviewing recent administrator activity.

A run of exploited VCO flaws

This is the third VCO zero-day Arista has reported as exploited since late July. Neither CVE-2026-16812 in July nor CVE-2026-93952 in September needed a login, unlike this one. Arista warned for those two flaws that a compromised orchestrator could also give attackers access to VeloCloud Edge devices; for this flaw the advisory says neither whether that risk applies nor whether upgrading removes access an attacker has already gained.

Arista acquired the VeloCloud SD-WAN line from Broadcom, announcing the deal in July 2025; the products were previously sold as VMware SD-WAN by VeloCloud.

What is not known yet

  • Who is carrying out the attacks and what they are seeking.
  • When exploitation started and how many orchestrators have been compromised.
  • What attackers did after gaining operator access, including whether they reached managed edge devices or read or changed data.
  • Whether installing a fixed release removes access an attacker has already established.
  • Whether the 6.1 train fix for this flaw also closes September's CVE-2026-93952.

What to do

If you run VeloCloud Orchestrator on-premises

  1. Upgrade to the fixed build for your release train; Arista lists one per train, with 6.4.2.12 covering the 6.4 train.
  2. Restrict access to the VCO web interface to trusted administrative networks.
  3. Block 74.82.197.86 and 38.54.50.151, and search VCO web access logs for them.
  4. Review recent administrator activity and logs for unusual URL-like path components, encoded characters, requests referencing internal services, and high request rates.

If you cannot patch immediately

  1. Watch for unexpected outbound traffic from the VCO host and block outbound ports that normal operation does not need.
  2. Look for backdoor daemons and webshells on the orchestrator.
  3. If compromise is suspected, preserve VCO web access, backend application, system and database logs and file-system timestamps before remediating, and contact Arista's Technical Assistance Center.

For everyone else

  1. Treat management portals for network equipment as high-value targets: keep them off untrusted networks, and assume a low-privilege login is enough for an attacker to escalate.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.