Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High ThreatIntel

Critical OS Command Injection (CVE-2026-16812) in Arista VeloCloud Orchestrator On-Prem Risks Enterprise SD‑WAN Control

Arista’s on‑prem VeloCloud Orchestrator is vulnerable to a remote OS command‑injection flaw (CVE‑2026‑16812) that could compromise confidentiality, integrity, and availability of the SD‑WAN control plane. The issue underscores the need for continuous vulnerability management and auditable remediation evidence for compliance and audit readiness.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
TI
Type
ThreatIntel
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
5 recommended
📰
Source
nvd.nist.gov

OS Command Injection (CVE‑2026‑16812) in Arista VeloCloud Orchestrator On‑Prem Threatens Enterprise SD‑WAN

What It Is — Arista’s VeloCloud Orchestrator (on‑premises deployment) contains an OS command‑injection flaw (CVE‑2026‑16812). An unauthenticated remote attacker can inject arbitrary operating‑system commands, potentially gaining privileged access to the orchestrator host.

Exploitability — The vulnerability is rated CVSS v3.1 8.8 (High) and is exploitable over the network; no public exploit has been observed, but the attack vector is remote and requires only network access to the orchestrator interface.

Affected Products — Arista VeloCloud Orchestrator (on‑premises version(s) listed in the CISA KEV advisory).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous vulnerability‑management controls that capture, prioritize, and remediate high‑severity flaws across critical network infrastructure.
  • Provides audit‑ready evidence that an organization is actively monitoring and patching SD‑WAN components, a key trust signal for enterprise buyers.
  • Highlights the importance of segregation and logging around orchestration platforms to limit the impact of a compromised host.

Recommended Actions

  • Review the Arista security advisory and apply any vendor‑released patches immediately.
  • Verify that your vulnerability‑scanning tools include the VeloCloud orchestrator in their asset inventory.
  • Enforce network segmentation for the orchestrator host and enable strict outbound command filtering.
  • Capture remediation evidence (patch version, scan results) in your control repository for audit readiness.
  • Update your incident‑response playbook to include OS‑command‑injection scenarios for SD‑WAN components.

Source: CISA KEV – CVE‑2026‑16812

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2026-16812 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →