Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-16812: Arista VeloCloud Orchestrator On-Prem OS Command Injection

Arista VeloCloud Orchestrator · listed in the CISA catalog of actively exploited vulnerabilities since 2026-07-27.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
1.8%
higher than 78.5% of all CVEs
Added to CISA KEV
2026-07-27
US federal due date 2026-07-30
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-16812 explained

CVE-2026-16812 is an OS command injection vulnerability in Arista VeloCloud Orchestrator (VCO) on-prem. Internal-only functionality is remotely reachable and lets an unauthenticated attacker affect the VCO host. The flaw is known to be actively exploited and is listed in CISA's Known Exploited Vulnerabilities catalog, so on-prem deployments need urgent attention.

Impact

A remote attacker without credentials or user interaction can reach privileged internal functionality over the network and affect the VCO host. This can compromise the confidentiality, integrity and availability of the orchestrator and the data it manages. The impact extends beyond the vulnerable component. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and gain full control. Active exploitation is confirmed.

Who is affected

Arista Networks VeloCloud Orchestrator On-Prem is affected in these ranges: ≥ 5.2.0, < 5.2.3.14, ≥ 6.1.0, < 6.1.3.4, ≥ 6.4.0, < 6.4.2.4 and ≥ 7.0.0, < 7.0.0.1. Fixed versions are 5.2.3.14, 6.1.3.4, 6.4.2.4 and 7.0.0.1. According to the description, Hosted and Dedicated versions of VCO were already patched before the notice was published.

Written with AI from the data on this page and checked against it automatically.

Official description

VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator.

This functionality was intended to be for internal use only and is not intended to be remotely accessible. Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out. This issue was discovered externally and is known to be actively exploited.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Arista Networks VeloCloud Orchestrator On-Prem
    Affected
    • ≥ 5.2.0, < 5.2.3.14
    • ≥ 6.1.0, < 6.1.3.4
    • ≥ 6.4.0, < 6.4.2.4
    • ≥ 7.0.0, < 7.0.0.1
    Fixed in
    • 5.2.3.14
    • 6.1.3.4
    • 6.4.2.4
    • 7.0.0.1

How to fix it

Vendor solution:

  • The recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.
  • This vulnerability has been fixed in the following releases: * VCO 5.2.3.14 and later in the 5.2 train * VCO 6.1.3.4 and later in the 6.1 train * VCO 6.4.2.4 and later in the 6.4 train

Workaround:

  • The recommended resolution is to upgrade to a fixed VCO release as soon as it is available.
  • For VCOs which are not on a supported release train, customers can contact TAC to discuss possible upgrade options for your release.
  • Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment: * Restrict access to the VCO web interface to trusted administrative networks. * Monitor the VCO for accesses from known malicious source IPs. * Monitor for unexpected outbound network activity from the VCO host. * Review recent administrator activity for unexpected changes.

What to do

  1. Upgrade VeloCloud Orchestrator On-Prem to the fixed version for your branch: 5.2.3.14, 6.1.3.4, 6.4.2.4 or 7.0.0.1.
  2. Apply any mitigations in the Arista advisory immediately if you cannot upgrade right away.
  3. Restrict network access to the orchestrator and keep it off the internet where possible.
  4. Check VCO hosts for signs of compromise, following CISA's forensics triage requirements, because the flaw is actively exploited.
  5. Discontinue use of the product if mitigations are unavailable, as CISA's required action states.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Questions about CVE-2026-16812

Are Hosted and Dedicated VCO deployments affected?
The description states that Hosted and Dedicated versions of VCO were already patched before the notice was published. The listed affected versions apply to VeloCloud Orchestrator On-Prem.
Is this vulnerability being exploited?
Yes. The description says it is known to be actively exploited. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-07-27, with a US federal due date of 2026-07-30. Whether ransomware groups use it is unknown.
Does an attacker need credentials?
No. The CVSS data shows network access with low complexity, no privileges and no user interaction. Unpatched orchestrators reachable over the network are at high risk.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.