Skip to content
major vulnerability· requires attention

10.0 CVSS OS command injection in Arista VeloCloud Orchestrator on‑prem; widely used SD‑WAN orchestration, CISA KEV and active exploitation — high org‑wide impact.

Infrastructure

CVE-2026-16812

CRITICAL
Critical
KEV · Exploited in wildEPSS 2%Patch availableJul 28, 2026

OS command injection in Arista VeloCloud Orchestrator (on‑prem) enabling full host compromise.

common questions

Is CVE-2026-16812 being exploited?

Yes. CVE-2026-16812 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-16812?

CVE-2026-16812 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-16812?

Yes. A fix has been recorded for CVE-2026-16812. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-16812 affect?

CVE-2026-16812 affects Arista VeloCloud Orchestrator (VCO) - On‑Prem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16812?

Apply vendor patches/mitigations immediately; isolate internet‑exposed VCO and follow CISA BOD 26‑04.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Arista VeloCloud Orchestrator (VCO) - On‑Prem
impact

Remote OS command injection allowing attackers to execute privileged commands, compromise orchestrator, access/modify configs and disrupt SD‑WAN services.

action required

Immediate action required

affected versions
Arista Networks VeloCloud Orchestrator On-Prem
  • affected>= 5.2.0 and < 5.2.3.14
  • affected>= 6.1.0 and < 6.1.3.4
  • affected>= 6.4.0 and < 6.4.2.4
  • affected>= 7.0.0 and < 7.0.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free