CVE-2026-93952: Arista VeloCloud Orchestrator Improper Input Validation Vulnerability

Arista VeloCloud Orchestrator changes a threat, product, or control assumption that should be translated into one explicit decision for the responsible team.

How to check your systems

Confirm the affected version and reachable component, preserve useful telemetry, apply the publisher guidance, and record the evidence used to close the item.

Record the running product build and enabled component from the vendor-supported inventory interface. Compare it with each affected range above, then check the documented authentication and network prerequisites. Keep the output, asset identifier, observation time, and advisory revision with the change ticket.

How to fix

Permanent remediation

The recommended resolution is to upgrade to a remediated VCO software version at your earliest convenience. These vulnerabilities have been fixed in the following releases: – VCO 5.2.3.16 and later in the 5.2.3 train – VCO 6.4.2.8 and later in the 6.4.2 train Releases in other release trains that fix this will be added over time. For VCOs not on a supported release train, customers can contact TAC to discuss possible upgrade options. CNA remediation guidance

1. Identify exact product versions, owners, exposure paths, and business-critical dependencies.
2. Apply the latest vendor remediation or isolate the vulnerable path when immediate patching is not possible.
3. Review available telemetry for exploitation attempts before restarting, rebuilding, or rotating evidence away.
4. Validate the fixed version and control health, then record any exception with an owner and expiry date.

Official remediation direction: CISA due date: 2026-09-25. This deadline applies to covered US federal civilian agencies; other organizations should set a risk-based deadline. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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. Official action

If you cannot patch yet

Until 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. – Consider blocking outbound ports not needed for normal activities. – Monitor for backdoor daemons and webshells. – Review recent administrator activity for unexpected changes. Published workaround

Give any temporary control an owner and expiry, verify it covers every affected instance, and retain a rollback path. Remove it only after the permanent remediation is verified.

Detection and post-fix validation

• Confirm the installed and running version of Arista VeloCloud Orchestrator against the current vendor advisory.
• Check whether the vulnerable interface is reachable from untrusted networks or lower-privileged identities.
• Look for new accounts, privilege changes, crashes, child processes, or unusual outbound traffic associated with the component.
• Run a post-remediation service and security-control health check and retain evidence with the change record.

A clean scan or a version match alone does not rule out earlier compromise. If telemetry suggests exploitation, preserve evidence and follow the incident-response process alongside patching.

Timeline and exploitation status

• September 22, 2026 — Source entry published.
• September 22, 2026 — Added to CISA KEV.
• September 22, 2026 — CVE record published.
• September 23, 2026 — Source record updated.

Record publication and KEV addition dates describe those source events; they do not establish when exploitation first began.

The linked official record reports exploitation in the wild. This does not establish that any particular deployment has been compromised.

Public proof-of-concept availability is not independently established here. Recheck the vendor and government records as evidence changes.

Primary sources and references

• CNA-linked reference: Security Advisory 0183
• CISA-linked vendor guidance: www.cisa.gov
• CISA-linked vendor guidance: www.cisa.gov
• CISA-linked vendor guidance: nvd.nist.gov
• CVE CNA: Arista: CVE-2026-93952 CNA record
• CISA Known Exploited Vulnerabilities: CVE-2026-93952: Arista VeloCloud Orchestrator Improper Input Validation Vulnerability