Advisory

CVE-2026-93952: CVSS 10 Critical Flaw in Arista VeloCloud Orchestrator — Patch Now

A critical improper input validation vulnerability (CVE-2026-93952) in Arista VeloCloud Orchestrator (VCO) on-premises deployments allows an unauthenticated remote attacker to access privileged internal functionality and fully compromise the orchestrator host. Successful exploitation threatens the confidentiality, integrity, and availability of the orchestrator and all data it manages.

TL;DR: On-premises VeloCloud Orchestrator operators must apply vendor-issued mitigations immediately in line with CISA KEV requirements and BOD 26-04 guidance; hosted/dedicated VCO instances have already been patched by Arista.

What Is CVE-2026-93952?

CVE-2026-93952 is an improper input validation vulnerability (CWE-20) in Arista's VeloCloud Orchestrator (VCO) on-premises product. It carries a CVSS 3.1 base score of 10.0 (Critical), the highest possible rating, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Breaking that vector down illustrates why this is so severe:

  • Network-accessible (AV:N): The attack surface is reachable over any network, including the public internet.
  • Low attack complexity (AC:L): No special conditions or race conditions are required.
  • No privileges required (PR:N): An attacker needs no existing account or credentials.
  • No user interaction (UI:N): The victim does not need to click anything or visit a page.
  • Changed scope (S:C): A successful attack can breach resources beyond the vulnerable component itself.
  • High impact across all three pillars (C:H/I:H/A:H): Full compromise of confidentiality, integrity, and availability is possible.

Improper input validation means the application fails to sufficiently check or sanitize input before acting on it, allowing an attacker to supply crafted input that triggers privileged internal functionality the attacker should never be able to reach.

Who and What Is Affected?

The vulnerability affects Arista VeloCloud Orchestrator (VCO) on-premises deployments. Organizations running self-hosted VCO instances must treat this as an urgent priority.

According to Arista's disclosure, hosted versions of VCO — including Dedicated instances — were also impacted but have already been patched by Arista. Customers on hosted or dedicated VCO should confirm with Arista that their instance is running the patched version; on-premises operators carry responsibility for applying the fix themselves.

VeloCloud Orchestrator is the centralized management and policy plane for Arista's SD-WAN solution. It orchestrates network connectivity, security policies, and configuration for potentially large numbers of branch edge devices. Compromise of the orchestrator therefore extends risk beyond the host itself to every managed edge and the data traversing those connections.

Deployment TypeStatus
On-Premises VCOVulnerable — patch required by operator
Hosted VCO (including Dedicated)Patched by Arista

What Is the Impact?

The NVD and CISA KEV entries are explicit: successful exploitation may compromise the confidentiality, integrity, and availability of both the orchestrator and the data it manages. In practical terms this means:

  • Privileged internal access: An unauthenticated remote attacker can reach internal functionality that should be restricted to administrators or the system itself.
  • Host-level impact: The VCO host — the server running the orchestrator — can be directly affected, not just the application layer.
  • Downstream SD-WAN exposure: Because VCO centrally manages edge devices and policies, a compromised orchestrator could be leveraged to manipulate network routing, exfiltrate managed configuration data, or disrupt branch connectivity.
  • Data managed by the orchestrator: Any data stored or processed through VCO — network topology, credentials, policy configurations — is at risk.

This vulnerability is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added on 2026-09-22, indicating that exploitation has been confirmed in the wild. Federal agencies subject to BOD 26-04 must prioritize remediation accordingly; all other organizations should treat KEV inclusion as a strong signal to act immediately.

What Should You Do Right Now?

CISA's required action for this KEV entry is clear: apply mitigations in accordance with vendor instructions, ensuring compliance with BOD 26-04 guidance and CISA's Forensics Triage Requirements, or discontinue use of the product if mitigations are unavailable.

  1. Identify all on-premises VCO instances in your environment. Cloud-managed or hosted instances should be verified with Arista as already patched.
  2. Consult the Arista security advisory for CVE-2026-93952 on Arista's official support portal to obtain the specific patched version(s) and any interim mitigations.
  3. Prioritize patching under BOD 26-04: Federal agencies must follow the patch timeline mandated by that directive. All organizations should treat this as an emergency change.
  4. Restrict network access to VCO management interfaces where patching cannot be immediately applied — ensure management planes are not exposed to untrusted networks.
  5. Review VCO logs and forensic artifacts per CISA's Forensics Triage Requirements, as KEV inclusion signals active exploitation. Look for anomalous access to privileged internal endpoints.
  6. Notify downstream stakeholders responsible for edge devices managed by the orchestrator so they can assess potential downstream impact.
  7. Monitor CISA KEV and Arista advisories for any updates to required actions or additional indicators.

Primary references: CISA KEV Catalog | NVD — CVE-2026-93952 | Arista official security advisories.

How Continuous External Testing Surfaces This Exposure

A CVSS 10 vulnerability with no authentication requirement and network-level access means that any VCO management interface reachable from the internet is immediately at risk. The challenge for many organizations is simply knowing which services are actually internet-exposed — asset inventories and firewall rule sets drift over time.

Continuous external attack surface monitoring and network/host testing addresses exactly this gap:

  • Internet-facing asset discovery: Regular scanning of your externally routable IP space identifies VCO instances or management ports that have inadvertently become internet-accessible, before an attacker finds them.
  • Service fingerprinting: Identifying the specific product and version running on exposed hosts lets you map your attack surface to published CVEs like CVE-2026-93952 without waiting for an internal vulnerability scan cycle.
  • Unauthenticated exposure checks: Testing whether endpoints respond to unauthenticated probes — consistent with the PR:N nature of this flaw — reveals whether the vulnerable surface is reachable.
  • Re-test after changes: Because infrastructure changes constantly, one-time assessments miss newly deployed or accidentally exposed instances. Re-running an external scan after changes catches drift between scheduled audits.
  • Prioritization signal: When a KEV-listed, CVSS 10 flaw is identified as present on an externally visible host, teams get an unambiguous signal to escalate remediation immediately.

For organizations managing SD-WAN infrastructure at scale, the orchestrator is the highest-value target. Ensuring it is never inadvertently exposed — and verifying that exposure continuously — is a foundational control.

Sources & further reading: NVD CVE-2026-93952 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: arista.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Is CVE-2026-93952 being actively exploited?

Yes. CVE-2026-93952 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-09-22, which indicates that exploitation has been confirmed. CISA and Arista advisories are the authoritative sources for the latest exploitation details.

Are cloud-hosted or dedicated VCO instances affected?

According to the Arista disclosure, hosted and dedicated VCO versions were impacted but have already been patched by Arista. Customers on those service tiers should confirm patch status with Arista directly. On-premises operators must apply patches themselves.

What does 'improper input validation' mean in practical terms for this flaw?

Improper input validation (CWE-20) means the application does not adequately verify or sanitize data it receives before processing it. In the context of CVE-2026-93952, this allows a remote attacker to craft input that the VCO treats as a legitimate request to privileged internal functionality — without any credentials or special access.

What is the BOD 26-04 obligation for federal agencies?

CISA's Binding Operational Directive 26-04 requires federal agencies to prioritize remediation of vulnerabilities listed in the KEV catalog based on risk, within defined timelines. For CVE-2026-93952, agencies must apply vendor mitigations or discontinue use if mitigations are unavailable, and follow CISA's Forensics Triage Requirements. Consult the official BOD 26-04 text on CISA.gov for specific deadlines.