An Arista zero-day, CVE-2026-16812, lets attackers run commands on VeloCloud Orchestrator, the control plane of the SD-WAN, without any credentials. Arista rated it CVSS 10.0, confirmed active exploitation on July 27, 2026, and published three attacker IP addresses. Patch to a fixed build, restrict the web interface, and investigate for compromise.
What Is CVE-2026-16812?
CVE-2026-16812 is an OS command injection flaw, CWE-78, in VeloCloud Orchestrator (VCO). Specifically, functionality meant for internal use turned out to be reachable through the VCO web interface, so an attacker can trigger it from outside without tenant or operator credentials. Arista scores it 10.0 on both CVSS 3.1 and CVSS 4.0, because the attack works over the network, needs no privileges and no user interaction, and changes scope beyond the orchestrator itself.
Why Does an Orchestrator Flaw Put the Whole SD-WAN at Risk?
However, VeloCloud Orchestrator is not just another server. Instead, it manages routing policy, device inventory, configuration, credentials, certificates and every connected VeloCloud Edge. Therefore, an attacker who owns the orchestrator can see, and potentially change, how branch offices, data centers and cloud sites talk to each other. Arista itself warns that a compromised VCO may give attackers access to the Edge devices as well, which is why this Arista zero-day reaches far beyond one host.
Which VeloCloud Orchestrator Versions Are at Risk?
Arista lists both VCO On-Prem and VCO Hosted as affected. In fact, revision 1.1 of the advisory, dated August 3, 2026, added Hosted to the affected platforms, and Arista patched hosted and dedicated instances itself. On premises customers must close the Arista zero-day themselves, and the table below collects the confirmed facts.
| Item | Detail |
|---|---|
| CVE | CVE-2026-16812, OS command injection (CWE-78) |
| CVSS | 10.0 on CVSS 3.1 and CVSS 4.0 |
| Authentication | None, only network access to the VCO web interface |
| Affected | VCO 5.2.x before 5.2.3.14, 6.1.x before 6.1.3.4, 6.4.x before 6.4.2.4, 7.0.x before 7.0.0.1 |
| Fixed builds | 5.2.3.14, 6.1.3.4 and 6.4.2.4 or later |
| Platforms | VCO On-Prem and VCO Hosted; Edge and Gateway not affected |
| Exploitation | Discovered externally and actively exploited, per Arista |
| Advisory | Arista Security Advisory 0144, July 27, 2026 |
| CISA KEV | Added July 27, 2026 |
Confirm every build against the official Arista Security Advisory 0144. In addition, Arista did not assess end of support versions, so treat those as exposed until Arista’s support team says otherwise.
Is the Arista Zero-Day Under Active Attack?
Yes. Arista states that outside parties discovered the flaw and that attackers actively exploit it, so attackers had it before defenders had a patch. Meanwhile, on the same day, CISA added CVE-2026-16812 to its catalog, and you can read the CISA alert on the July 27 additions. Arista also published three IP addresses confirmed to have exploited the flaw, while warning that the list is not exhaustive. Therefore, block them now and search your history for them.
Was This the Only VeloCloud Orchestrator Zero-Day?
No, and that matters for anyone who patched in July and stopped. Since this Arista zero-day, two more actively exploited VCO flaws have landed. First, CVE-2026-93952, a certificate authentication bypass rated 10.0, arrived in September. Then CVE-2026-114625, an SQL injection rated 9.9 that any logged in user can trigger, arrived in October, and Canada’s Centre for Cyber Security issued alert AV26-1080 on it. The July builds do not fix the later flaws, so run the newest build in your train, such as 5.2.3.18, 6.1.3.10 or 6.4.2.12 for the October fix.
How Strong Is the Evidence?
We separate confirmed facts from open questions, so you can judge the Arista zero-day yourself.
- Confirmed by Arista: the flaw and its CWE, the 10.0 scores, the affected and fixed builds, the On-Prem and Hosted platforms, active exploitation, the three attacker IP addresses, and the log guidance
- Confirmed by CISA: the July 27, 2026 addition to the Known Exploited Vulnerabilities catalog
- Still open: the advisory lists 7.0.x as affected but names no fixed 7.0 build in its resolution section, it mentions dedicated instances without listing them, and Arista has not said who exploited the flaw or how many customers it reached
How Do You Respond to CVE-2026-16812?
Treat the Arista zero-day as an incident, not a routine patch. Work through these steps in order.
- Patch now: upgrade every on premises VCO to the newest build in its train, which also covers the September and October flaws
- Restrict access: limit the VCO web interface to trusted administrative networks and remove any internet exposure, because no VCO setting prevents the flaw
- Block the IPs: block the three published addresses and search firewall, proxy and web logs for past contact
- Preserve evidence first: if you suspect compromise, save web access, application, system and database logs plus file timestamps before you change anything
- Hunt the logs: look for encoded characters, URL like path parts, references to internal services, high request rates, unexpected outbound HTTP or HTTPS, new archives and database exports
- Rotate and validate: rotate credentials, certificates and keys the orchestrator held, and check every connected Edge for unauthorized changes
For more on choosing which flaws to drop everything for, our 2026 Mid Year Threat Pattern Report found that attackers weaponized eight of eleven zero days, or 73 percent, within 72 hours of disclosure. Therefore, an Arista zero-day this severe belongs in emergency change control.
What Should Your Team Do Now?
Above all, treat SD-WAN management the way you treat domain administration: restricted, monitored and tested. Our team runs penetration testing and vulnerability assessments that show whether an attacker can still reach your orchestrator and what sits behind it after an Arista zero-day, and our PTaaS platform keeps that testing continuous between audits.
Key Takeaways
- CVE-2026-16812 lets an unauthenticated attacker run commands on VeloCloud Orchestrator, and Arista rates it CVSS 10.0
- Arista confirmed active exploitation on July 27, 2026, published three attacker IPs, and CISA listed the flaw the same day
- VCO On-Prem and Hosted are affected; Edge and Gateway are not, but a compromised orchestrator can expose them
- Two more exploited VCO zero-days followed in September and October, so run the newest build, not the July one
- Patch, restrict the web interface, preserve evidence, hunt the logs, then rotate credentials and validate Edges
Frequently Asked Questions About the Arista Zero-Day
What is the Arista zero-day CVE-2026-16812?
It is an OS command injection flaw in on premises and hosted VeloCloud Orchestrator, rated CVSS 10.0. An attacker who can reach the VCO web interface can run commands on the host without any tenant or operator credentials.
Which VeloCloud Orchestrator versions fix CVE-2026-16812?
Arista fixed it in 5.2.3.14, 6.1.3.4 and 6.4.2.4. Because two more VCO zero-days followed, move to the newest build in your train rather than stopping at those versions.
Are attackers exploiting CVE-2026-16812?
Yes. Arista says outside parties discovered the flaw and that attackers actively exploit it, and CISA added it to the Known Exploited Vulnerabilities catalog on July 27, 2026.
Are VeloCloud Edge and Gateway devices affected?
Arista lists them as not vulnerable to this flaw. However, it warns that a compromised orchestrator may give attackers access to the Edge devices it manages, so validate them after an incident.
Is there a workaround for the flaw?
No VCO setting prevents exposure to the Arista zero-day. Restricting the web interface to trusted administrative networks reduces risk, but only patching closes it.
Does patching end the incident?
Not if attackers got in first. Preserve logs, look for the published indicators, rotate credentials, certificates and keys the orchestrator held, and check connected Edge devices for changes.

