‹ All news

Follow-up · active exploitationCritical

Attackers exploit a critical VeloCloud Orchestrator flaw that grants operator privileges

CISA has confirmed active exploitation of CVE-2026-114625, a critical flaw (CVSS 9.4) in on-premises VeloCloud Orchestrator deployments. It lets any authenticated user impersonate a top-privileged operator. Organisations that run this SD-WAN orchestrator on their own infrastructure are affected.

What happened

On 23 October 2026, the US agency CISA added CVE-2026-114625 to its Known Exploited Vulnerabilities (KEV) catalogue, which lists flaws with confirmed active exploitation. The vulnerability affects on-premises deployments of VeloCloud Orchestrator (VCO), the central management console for SD-WAN networks. It was published in NVD on 22 October with a critical CVSS score of 9.4.

According to the published description, any authenticated user on an affected system can gain operator privileges and impersonate the local "superuser operator" account. This exposes functionality meant for internal use only, which should never be reachable remotely. Successful exploitation can compromise the confidentiality, integrity and availability of the orchestrator, the data it manages and the host it runs on.

Exploitation status

Exploitation has been confirmed by CISA, which has set 26 October 2026 as the remediation deadline for US federal agencies. It is not known whether the flaw is being used in ransomware campaigns, and no public exploit is known. Three different specialist outlets have reported on it over the past week.

FIRST's EPSS model currently gives it a low probability of exploitation (0.6% over the next 30 days). However, CISA's confirmation outweighs this statistical estimate: the flaw is already being abused, and an attacker only needs a low-privileged account.

Who is affected

Organisations running VeloCloud Orchestrator on their own infrastructure are affected. Hosted versions, including Dedicated ones, were also vulnerable, but they have already been patched, so those customers do not need to take action.

The available information does not specify which on-premises versions are affected or which releases contain the fix. The NVD entry points to an Arista security advisory, which is the place to check these details.

What to do

Given the active exploitation, this should be handled urgently, using CISA's deadline as a benchmark.

  • Identify every on-premises VeloCloud Orchestrator instance and confirm its version.
  • Check the vendor advisory for the fixed release and apply it as soon as possible.
  • In the meantime, restrict access to the orchestrator's management interface: keep it off the internet and reachable only from trusted administration networks.
  • Review orchestrator user accounts, remove those that are not needed and reset passwords for any that may be compromised.
  • Review logs for unusual activity with operator privileges or access to internal functions, and treat any sign of it as a potential incident.

Vulnerabilities (1)

CVESeverityActive exploitationPublishedNVD status
CVE-2026-114625Critical (9.4)⚠ Active exploitation10/22/2026Analyzed

Written automatically from NVD, CISA KEV and vendor advisory data. Always check affected versions and patches in the vendor's official advisory before acting.