Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2026-16812: Unauthenticated OS Command Injection in Arista VeloCloud Orchestrator

Published Jul 27, 2026 · Updated 17 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v4
EPSS1.8%78th percentile
CISA KEVYesAdded Jul 27, 2026
In the wildActivePer CISA KEV
Vendor
Arista Networks
IdentifiersCVE-2026-16812CWE-78 · Improper Neutralization of Special…

CVE-2026-16812 is an unauthenticated operating system command injection vulnerability in on-premises Arista VeloCloud Orchestrator (VCO). Privileged backend functionality intended only for internal use is remotely accessible through the VCO web interface, allowing attacker-controlled input to reach operating system command execution. A remote attacker can execute arbitrary commands on the orchestrator host without tenant or operator credentials. Affected release trains are 5.2.x before 5.2.3.14, 6.1.x before 6.1.3.4, 6.4.x before 6.4.2.4, and 7.0.x before 7.0.0.1. The precise vulnerable endpoint and implementation details are not publicly available. The vulnerability is actively exploited and has a CVSS score of 10.0 under both CVSS v3.1 and v4.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the confidentiality, integrity, and availability of the VCO host and its managed data. Command execution occurs with the privileges of the affected service and may permit software installation, account creation, database access, data modification or deletion, and persistence. Compromise of this centralized SD-WAN management platform may expose configurations, credentials, certificates, cryptographic keys, and network inventory. Attackers may also abuse the orchestrator's trusted administrative capabilities to alter managed Edge configurations, routing, firewall policies, or VPN settings, potentially disrupting multiple sites. VeloCloud Gateway and Edge appliances are not directly vulnerable to this flaw, but managed Edge devices may be affected through a compromised orchestrator.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, restrict the VCO web interface to trusted administrative networks using firewalls, IP allowlists, VPNs, or dedicated management networks. No VCO configuration change eliminates the underlying vulnerability. Review web access, backend application, and system logs for suspicious requests and activity; monitor unexpected outbound connections, service-spawned shells, account changes, certificate changes, and unauthorized device configurations. Centralize and retain logs outside the orchestrator, segment management infrastructure, and apply least privilege to service accounts. Block known malicious sources as an additional control, but do not treat their absence as evidence that a deployment is uncompromised.

Remediation

Patch, then assume compromise.

Upgrade affected on-premises VCO deployments to a fixed release within the applicable branch: 5.2.3.14 or later for 5.2.x, 6.1.3.4 or later for 6.1.x, 6.4.2.4 or later for 6.4.x, or 7.0.0.1 or later for 7.0.x. Hosted and Dedicated VCO services were patched before public disclosure. End-of-support releases have not been assessed; contact Arista for upgrade guidance. If compromise is suspected, preserve logs and file-system timestamps before remediation where feasible, investigate persistence and unauthorized administrative changes, rotate exposed authentication material, and validate managed-device integrity. Patching alone does not remove existing attacker access.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Arista NetworksVelocloud Orchestratorapplication
FAQ

Frequently asked questions

Is CVE-2026-16812 exploited in the wild?
Yes. As of Oct 31, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 27, 2026.
Is there a public exploit for CVE-2026-16812?
As of Oct 31, 2026, Mallory has found no public exploit for CVE-2026-16812.
Is there a patch for CVE-2026-16812?
Upgrade affected on-premises VCO deployments to a fixed release within the applicable branch: 5.2.3.14 or later for 5.2.x, 6.1.3.4 or later for 6.1.x, 6.4.2.4 or later for 6.4.x, or 7.0.0.1 or later for 7.0.x. Hosted and Dedicated VCO services were patched before public disclosure.
What products are affected by CVE-2026-16812?
Arista Networks Velocloud Orchestrator.
How severe is CVE-2026-16812?
CVE-2026-16812 has a CVSS v4 score of 10.0 (Critical) and an EPSS score of 1.8% (78th percentile) as of Oct 31, 2026.
Activity feed

Recent activity

125 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence8Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.