A Critical Arista VeloCloud Zero-Day Is Under Active Attack: What to Do Now

A critical zero-day affecting Arista VeloCloud Orchestrator is under active exploitation. Learn who is exposed, what immediate actions to take and why rapid detection is just as important as patching.
Arista VeloCloud Zero-Day Under Active Attack

In early August 2026, attackers began actively exploiting a maximum-severity zero-day in Arista VeloCloud Orchestrator (CVE-2026-16812), an internet-facing SD-WAN management platform. The flaw allows unauthenticated attackers to execute operating system commands remotely. Organisations should patch immediately, determine whether their orchestrator was exposed to the internet and investigate for signs of compromise.

What Happened?

Organisations using Arista VeloCloud Orchestrator (VCO) On-Prem should treat this vulnerability as an immediate priority.

Arista has disclosed CVE-2026-16812, a CVSS 10.0 operating system command injection vulnerability affecting on-premises deployments of VeloCloud Orchestrator. The company confirmed that the vulnerability is actively exploited in the wild, and CISA rapidly added it to its Known Exploited Vulnerabilities (KEV) Catalog, giving U.S. federal agencies only a short remediation window, highlighting the seriousness of the threat.

The vulnerability affects on-premises VeloCloud Orchestrator deployments only. According to Arista, Hosted and Dedicated VCO services had already been patched before the advisory was published.

The flaw exists because functionality intended only for internal use can be accessed remotely, allowing an unauthenticated attacker with network access to the VCO web interface to execute operating system commands and potentially compromise the orchestrator itself. Since the orchestrator manages SD-WAN infrastructure, successful exploitation may affect both the management platform and the networks it controls.

For organisations relying on SD-WAN to connect offices, cloud environments and remote users, this is not simply another software vulnerability. It is an attack against the control plane of the network.


Why Network Management Platforms Are High-Value Targets

Security teams often focus on protecting endpoints, servers and cloud workloads.

However, attackers increasingly target management infrastructure because compromising one administrative platform can provide visibility and control across an entire environment.

An SD-WAN orchestrator typically manages:

  • Network configuration
  • Edge device provisioning
  • Routing policies
  • VPN connectivity
  • Security settings
  • Software updates
  • Administrative credentials

If attackers compromise this platform, they may gain the ability to manipulate network traffic, access sensitive configuration data, deploy malicious changes or pivot into managed environments.

These platforms are particularly attractive because they are frequently internet accessible to support remote administration across distributed organisations.

When management systems are exposed directly to the internet, vulnerabilities become significantly more valuable to attackers.


How Unauthenticated Remote Command Execution Is Exploited

One reason CVE-2026-16812 has received maximum severity ratings is that exploitation does not require authentication.

According to Arista, an attacker only requires network access to the vulnerable web interface. Tenant credentials, operator accounts and valid sessions are not required for successful exploitation.

This dramatically lowers the barrier for attackers.

Instead of stealing credentials or exploiting multiple weaknesses, attackers can attempt to compromise exposed systems directly through specially crafted requests.

Successful exploitation may allow attackers to:

  • Execute operating system commands.
  • Compromise the orchestrator server.
  • Access configuration information.
  • Modify SD-WAN policies.
  • Pivot into connected environments.
  • Maintain persistent access.

The combination of internet exposure, privileged access and unauthenticated exploitation explains why CISA rapidly classified the vulnerability as actively exploited.


Who Is Exposed?

Not every VeloCloud deployment is affected.

The advisory applies specifically to Arista VeloCloud Orchestrator On-Prem installations running affected software versions.

Organisations should immediately determine:

  • Whether they operate an on-premises VCO instance.
  • Whether the deployed version is listed as vulnerable.
  • Whether the management interface is accessible from the internet.
  • Whether emergency patches have been applied.

Hosted VCO services and VeloCloud Edge appliances themselves are not affected by this vulnerability.

Organisations operating large branch networks, managed service providers, telecommunications providers and enterprises using SD-WAN across multiple locations are among those most likely to be affected if they manage their own on-premises orchestrator.

Immediate Actions

If your organisation operates an on-premises Arista VeloCloud Orchestrator, the priority should be to assume the vulnerability may already be under active targeting.

Arista recommends applying the vendor’s security update as soon as possible. If patching cannot occur immediately, organisations should reduce exposure by ensuring the management interface is not directly accessible from the public internet and restricting administrative access to trusted networks only. (Arista Security Advisory)

Security teams should also investigate whether exploitation has already occurred. This includes reviewing authentication and system logs for unusual activity, identifying unexpected administrative accounts, checking for unauthorised configuration changes, and looking for indicators that operating system commands were executed outside normal administrative activity.

Recommended actions include:

  • Apply the latest security update from Arista immediately.
  • Remove public internet exposure of the VCO management interface wherever possible.
  • Restrict administrative access using VPNs or trusted management networks.
  • Review authentication and audit logs for suspicious activity.
  • Hunt for web shells, unauthorised files and newly created administrator accounts.
  • Rotate privileged credentials if compromise is suspected.
  • Validate the integrity of SD-WAN configurations and connected edge devices.

Organisations should also remember that patching removes the vulnerability but does not remove an attacker who may already have gained access before the update was applied. Incident response activities should therefore include compromise assessment as well as remediation.

Why Continuous Monitoring Matters When Exploitation Has Already Begun

Once attackers begin exploiting a vulnerability in the wild, the window between disclosure and compromise becomes much shorter.

Many organisations focus on patch management alone, but attackers frequently exploit vulnerabilities within hours of public disclosure. Even well-managed environments can experience delays due to change management, maintenance windows or operational constraints.

This is why managed detection and response plays an important role alongside vulnerability management.

Continuous monitoring helps organisations identify suspicious behaviour that may indicate exploitation before widespread damage occurs. Rather than relying solely on vulnerability scans, MDR services monitor endpoints, servers and network activity for indicators such as:

  • Unusual administrative activity.
  • Unexpected command execution.
  • New privileged accounts.
  • Suspicious outbound network connections.
  • Attempts to establish persistence.
  • Lateral movement between systems.

Where internet-facing infrastructure is involved, organisations should also conduct regular penetration testing to identify externally exposed management interfaces and validate whether critical systems can be reached from the public internet. Penetration testing provides evidence of real-world exposure before attackers discover it themselves.

The combination of timely patching, secure network architecture, continuous monitoring and proactive security testing provides significantly stronger protection than relying on any single security control.

Frequently Asked Questions

What is CVE-2026-16812?

CVE-2026-16812 is a maximum-severity (CVSS 10.0) vulnerability affecting Arista VeloCloud Orchestrator On-Prem. The flaw allows unauthenticated attackers with network access to the web interface to execute operating system commands remotely and potentially compromise the orchestrator. Arista has confirmed active exploitation. (Arista Security Advisory)

Why are SD-WAN and network appliances targeted?

Network management platforms control critical infrastructure, including routing, VPN connectivity, configuration management and administrative access. Because they often manage multiple locations and may be internet accessible, compromising a single appliance can provide attackers with broad control across an organisation’s network.

What should I do if I run VeloCloud Orchestrator?

Apply Arista’s security update immediately, confirm whether the management interface is publicly accessible, restrict administrative access, review authentication and audit logs, and investigate for indicators of compromise such as unexpected accounts, suspicious commands or unauthorised configuration changes.

How do I know if I was compromised?

Review system logs for unusual administrative activity, investigate newly created user accounts, check for unexpected configuration changes, inspect the server for web shells or unauthorised files, and monitor for suspicious outbound network activity. If compromise is suspected, initiate a full incident response investigation rather than relying on patching alone.

How Intrix Can Help

Active exploitation of internet-facing infrastructure leaves little time for organisations to react. When vulnerabilities like CVE-2026-16812 are already being used by attackers, rapid detection and response become just as important as applying the vendor patch.

Intrix’s Managed Detection and Response service provides continuous monitoring to identify suspicious activity across your environment, helping security teams detect exploitation attempts, investigate potential compromise and respond before attackers can establish persistence or move laterally. Our analysts work alongside your internal teams to reduce dwell time and improve incident response readiness.

To reduce future exposure, Intrix also delivers Penetration Testing services that identify internet-facing vulnerabilities, validate exploitability and uncover security weaknesses before attackers do. Combined with ongoing monitoring and proactive testing, organisations can strengthen their resilience against rapidly emerging threats targeting critical infrastructure.

author avatar
Edward Ye

Edward Ye

Share this post

Other Insights

Vulnerability Assessment vs Penetration Testing What's the Difference

Vulnerability Assessment vs Penetration Testing: What’s the Difference?

Vulnerability assessments identify potential weaknesses, while penetration testing validates what an attacker could actually exploit. Learn how they differ and why organisations often benefit from both.
The Essential Eight Explained: A Guide for Australian Businesses

The Essential Eight Explained

The Essential Eight provides Australian organisations with eight practical cyber security strategies to reduce risk. Learn what each strategy covers, how maturity levels work and how to start improving your security posture.

Stay Informed with Our Security Newsletter

Get the latest threat intelligence, security insights, and industry updates delivered directly to your inbox.

Scroll to Top