VeloCloud SD-WAN Orchestrator flaw exploited: what to do

By the NexusSec team · 3 min read · Published
Short version: Arista disclosed CVE-2026-114625 on 22 October 2026: a SQL injection flaw in the on-premises VeloCloud SD-WAN Orchestrator that lets any logged-in user, even a read-only one, gain operator privileges. It is being exploited, CISA added it to its exploited list on 23 October, and it is the third exploited VeloCloud Orchestrator flaw reported in about four months. Upgrade on-premises orchestrators to the fixed release in Arista's advisory, and restrict who can reach them.

An SD-WAN orchestrator controls every branch and every link it manages. That makes it one of the most valuable systems on a multi-site network, and one of the most dangerous to leave exposed. This post reflects what was published up to 1 November 2026.

What happened

Arista published security advisory 0199 on 22 October 2026 for CVE-2026-114625, a SQL injection flaw in the on-premises VeloCloud Orchestrator, and said it is known to be exploited. Arista rates it 9.9 under CVSS v3.1 and 9.4 under CVSS v4.0. CISA added it to its Known Exploited Vulnerabilities catalogue on 23 October.

According to the advisory as reported, any authenticated user, down to the lowest Enterprise Read Only role, can gain operator privileges and pose as a local superuser operator. That opens internal-only functions that could compromise the orchestrator host and the data it manages. The on-premises orchestrator is vulnerable by default, and no configuration change removes the exposure.

Who is affected

A pattern worth noticing

Reporting describes this as the third exploited VeloCloud Orchestrator flaw in about four months, after CVE-2026-16812 in July and CVE-2026-93952 in September.

What to do

  1. Upgrade on-premises orchestrators to the fixed release for your software train listed in Arista's advisory 0199. Secondary reports give different build numbers, so take them from Arista. If you run an end-of-support version, contact Arista TAC.
  2. Restrict access to the orchestrator's web interface to management networks or a VPN.
  3. Review orchestrator accounts. Remove the ones nobody uses, and remember that a read-only account was enough for this flaw.
  4. Review recent operator activity and configuration pushed to edges for anything you did not expect.
  5. Enforce MFA for orchestrator logins where it is supported.

The lesson for any SD-WAN

Whatever platform you run, the management plane deserves the strongest protection on the network: not reachable from the internet, few accounts, MFA, logging and fast patching. See site-to-site VPN mistakes, SD-WAN vs MPLS and our SD-WAN implementation service.

Sources

Frequently asked questions

Are VeloCloud Edges or Gateways affected by CVE-2026-114625?

They are reported as not affected. The flaw is in the VeloCloud Orchestrator.

Is the hosted VeloCloud Orchestrator affected?

Hosted orchestrators, including dedicated ones, were affected but had already been patched by Arista. On-premises orchestrators need upgrading.

Which version fixes it?

Use the fixed release for your train listed in Arista security advisory 0199. Secondary reports quote different build numbers, so take them from Arista.

Why does a read-only account matter here?

According to the advisory as reported, even the lowest Enterprise Read Only role was enough to gain operator privileges, so every account is a possible way in.

Running SD-WAN across several sites?

We review how your SD-WAN and its management are exposed, and lock down access to the orchestrator and edge devices.

Book a free consultation