Skip to content
Server Security Center
KEVcritical10.0

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

Arista VeloCloud Orchestrator · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-22.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
1.4%
higher than 72.8% of all CVEs
Added to CISA KEV
2026-09-22
US federal due date 2026-09-25
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-93952 explained

CVE-2026-93952 is an improper input validation flaw in Arista VeloCloud Orchestrator (VCO) on-prem. It may let a remote attacker reach privileged internal functionality and affect the VCO host, putting the orchestrator and the data it manages at risk. CISA lists it as known to be exploited, so it needs urgent attention.

Impact

A remote attacker with no privileges and no user interaction can access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity and availability of the orchestrator and the data it manages. The scope is changed, so effects can reach beyond the vulnerable component. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and gain full control.

Who is affected

Arista Networks VeloCloud Orchestrator (VCO) On-Prem is affected in four branches. These are 5.2.0 up to and including 5.2.3.15, 6.1.0 up to and including 6.1.3.7, 6.4.0 up to and including 6.4.2.7, and 7.0.0 up to and including 7.0.0.2. The CVE record names no fixed version. The description states that hosted VCO, including Dedicated, was also affected and has already been patched.

Written with AI from the data on this page and checked against it automatically.

Official description

VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue 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.

Hosted, including Dedicated, versions of VCO were impacted and have already been patched.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Arista Networks VeloCloud Orchestrator (VCO) On-PremVeloCloud Orchestrator On-Prem
    Affected
    • ≥ 5.2.0, ≤ 5.2.3.15
    • ≥ 6.1.0, ≤ 6.1.3.7
    • ≥ 6.4.0, ≤ 6.4.2.7
    • ≥ 7.0.0, ≤ 7.0.0.2
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: arista.com/en/support/advisories-notices/security-advisor…
  • CISA's deadline for US federal agencies: 2026-09-25 (passed) – a useful benchmark for everyone else, too.

Vendor solution:

  • 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.

Workaround: 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.

What to do

  1. Identify all on-prem VeloCloud Orchestrator instances and check their versions against the affected ranges.
  2. Follow the Arista vendor advisory and apply its fixed releases or mitigations as soon as possible.
  3. Restrict network access to the orchestrator so it is not reachable from the internet or untrusted networks.
  4. Check orchestrator hosts for signs of compromise, in line with CISA's forensics triage requirements.
  5. If mitigations are unavailable, discontinue use of the product as CISA's required action directs.

The CVE record names no fixed version for VCO On-Prem. Follow the Arista vendor advisory for updates and mitigations. CISA requires applying mitigations according to vendor instructions, or discontinuing use of the product if mitigations are unavailable. Until then, limit network exposure of the orchestrator and check for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-20 Improper Input Validation

Questions about CVE-2026-93952

Is this vulnerability being exploited?
Yes. CISA added CVE-2026-93952 to its Known Exploited Vulnerabilities catalog on 2026-09-22, with a US federal due date of 2026-09-25. Whether it is used in ransomware campaigns is unknown.
Do hosted VCO customers need to act?
According to the description, hosted VCO, including Dedicated, was affected and has already been patched. The listed affected versions apply to VeloCloud Orchestrator (VCO) On-Prem.
Does an attacker need credentials?
No. The CVSS vector shows network attack, low complexity, no privileges and no user interaction required. That makes exposed on-prem orchestrators a high priority.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.