← All Advisories

Arista VeloCloud Orchestrator Input Validation Gap Lets Remote Attackers Reach Privileged APIs; CISA's September 25th KEV Deadline for Covered Entities Has Now Passed

Last refreshed2026-09-27

Status: KEV  |  Advisory ID: CVE-2026-93952

Key Details

CVECVE-2026-93952
Vulnerability NameArista VeloCloud Orchestrator Improper Input Validation Vulnerability
Affected productsArista VeloCloud Orchestrator
Exploitation statusListed in CISA's Known Exploited Vulnerabilities (KEV) catalog, indicating confirmed active exploitation.
Classified asCWE-20 (Improper Input Validation)
KEV listingAdded to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-09-22.
Exploitation prediction (EPSS)0.90% probability of exploitation in the next 30 days (58% percentile) -- FIRST.org's EPSS model.
Federal remediation deadline2026-09-25 (CISA KEV, Binding Operational Directive).

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
AristaVeloCloud Orchestrator
SubsystemsGeneral OT
SectorsMultiple

What to Know

Arista VeloCloud Orchestrator (VCO) on-prem contains an improper input validation vulnerability that 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.

What to Do

Monitor Arista's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-93952
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-93952

KEV Required Action

FieldValue
KEV Linkhttps://www.cisa.gov/known-exploited-vulnerabilities-catalog
Date Added to KEV2026-09-22
Required Action Due Date2026-09-25
Required ActionApply 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.