CVE Intelligence
CISA KEV Critical Input validation

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

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.

Published Sep 22, 2026 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: Arista

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 1.1% (30-day exploitation probability)+10
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Sep 22, 2026
EPSS FIRST
1.06%
ahead of 64% of scored CVEs · Oct 14, 2026
Affects
Arista
Velocloud Orchestrator and 1 more
CVSS base
10.0
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — www.arista.com (NIST National Vulnerability Database)

CISA required action CISA

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.

US federal deadline: Sep 25, 2026 — passed 20 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Arista Velocloud Orchestrator, Arista Networks VeloCloud Orchestrator (VCO) On-Prem).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the documented mitigations until a definitive fix is available.
  5. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Arista Velocloud Orchestrator ≥ 5.2.0 and < 5.2.3.16≥ 6.1.0 and ≤ 6.1.3.7≥ 6.4.0 and < 6.4.2.8≥ 7.0.0 and ≤ 7.0.0.2 Vulnerable NIST National Vulnerability Database
Arista Networks VeloCloud Orchestrator (VCO) On-Prem ≥ 5.2.0 and ≤ 5.2.3.15≥ 6.1.0 and ≤ 6.1.3.7≥ 6.4.0 and ≤ 6.4.2.7≥ 7.0.0 and ≤ 7.0.0.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.5 CVSS 4.0 Critical — — psirt@arista.com via NIST National Vulnerability Database
9.5 CVSS 4.0 Critical — — Arista via CVE Program (cve.org) e CISA ADP
10.0 CVSS 3.1 Critical 3.9 6.0 psirt@arista.com via NIST National Vulnerability Database
10.0 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
10.0 CVSS 3.1 Critical — — Arista via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: psirt@arista.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Sep 22, 2026
Federal deadline
Sep 25, 2026
passed 20 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.06%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Sep 22, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · arista networks/velocloud orchestrator (vco) on-prem
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · arista/velocloud orchestrator
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 10.0
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • CVE published
    Sep 22, 2026 · Arista
  • Added to CISA KEV catalog
    Sep 21, 2026 · CISA

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Arista
every CVE for this vendor
2026-09
what else CISA listed that month
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-16812 Arista VeloCloud Orchestrator On-Prem OS Command Injection Vulnerability KEV Jul 27, 2026
  • High CVE-2026-31431 Linux Kernel Incorrect Resource Transfer Between Spheres Vulnerability KEV Apr 22, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93952 is "Arista VeloCloud Orchestrator Improper Input Validation Vulnerability", rated Critical. It affects Velocloud Orchestrator (Arista); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 1.06% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.