CVE-2026-93952

CRITICAL(10.0)KEV

Arista VeloCloud Orchestrator Improper Input Validation Vulnerability

Description

CVE-2026-93952 is a maximum-severity improper input validation vulnerability in on-premises Arista VeloCloud Orchestrator (VCO) that allows a remote attacker to reach privileged internal functionality and impact the VCO host. Arista states that successful exploitation may compromise the confidentiality, integrity and availability of the orchestrator and of the data it manages. Hosted and Dedicated VCO instances were also affected and have already been patched by Arista; on-premises deployments must be updated by their operators. Because VeloCloud Orchestrator is the management plane of an SD-WAN, compromising it reaches every edge device and tunnel it controls. CISA has added CVE-2026-93952 to the Known Exploited Vulnerabilities catalog, and its remediation deadline of September 25, 2026 has already passed.

KEV Information

Vendor
Arista
Product
VeloCloud Orchestrator
Date Added
September 22, 2026
Due Date
September 25, 2026
Required Action
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.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
3.9
Impact Score
6.0

CWEs

Affected Products

VendorProductVersion
aristavelocloud orchestrator>= 5.2.0, < 5.2.3.16; >= 6.1.0, <= 6.1.3.7; >= 6.4.0, < 6.4.2.8; >= 7.0.0, <= 7.0.0.2

References

Weakness Type

CWE-20: Improper Input Validation

Improper input validation occurs when software accepts data without confirming that it has the properties required to process it safely — the expected format, type, length or range. In VeloCloud Orchestrator, input reaching the affected path is not validated against such constraints, and the result is that a remote request obtains access to privileged internal functionality that the orchestrator was never meant to expose to it.

Learn more: CWE-20 — Improper Input Validation

Impact Analysis

CVE-2026-93952 has a CVSS 3.1 base score of 10.0 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H — the highest the scale allows. Attack Vector (Network), Privileges Required (None), User Interaction (None), Attack Complexity (Low): no credential, no victim, no special condition; reaching the orchestrator over the network is the only requirement. Scope (Changed) is what takes the score to 10.0 and is well founded here: the impact extends past the vulnerable component into the SD-WAN fabric the orchestrator governs, since control of VCO means control of the configuration pushed to edge devices. Confidentiality, Integrity and Availability (all High): Arista names all three explicitly for both the orchestrator and the data it manages — that data includes the topology, credentials and policy of a customer's or a service provider's entire wide-area network. For managed service providers running multi-tenant VCO installations, the exposure is multiplied across customers. The EPSS score of 1.06% in the 64th percentile is modest, but the KEV listing confirms real exploitation and the deadline has already lapsed.

Exploit Maturity

CISA has added CVE-2026-93952 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 25, 2026 has already passed; the entry does not flag use in ransomware campaigns. The references are Arista Security Advisory 0183, which also carries mitigation guidance, and the CISA catalog entry — no public proof-of-concept is listed. The EPSS score of 1.06% places the vulnerability in the 64th percentile, above the median but far below what a 10.0-rated unauthenticated flaw might suggest; EPSS is driven by observable mass exploitation, and VeloCloud Orchestrator is a specialized product with a comparatively small, high-value installed base rather than a broadly scanned one. That profile argues for targeted rather than opportunistic attacks, which is the more dangerous shape for the organizations concerned: service providers and enterprises whose entire WAN configuration lives in the orchestrator.

Remediation

  1. Carry out the action CISA requires, immediately. Apply mitigations in accordance with Arista's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of September 25, 2026 has already passed.
  2. Upgrade on-premises VeloCloud Orchestrator to a fixed release. The published version data covers 5.2.0 up to 5.2.3.16, 6.1.0 through 6.1.3.7, 6.4.0 up to 6.4.2.8 and 7.0.0 through 7.0.0.2; the fixed builds and any interim mitigations are listed in Arista Security Advisory 0183. Hosted and Dedicated instances have already been patched by Arista and require no customer action for this issue.
  3. Restrict who can reach the orchestrator while you upgrade. The VCO management interface should be reachable only from a dedicated management network or through a VPN; taking it off any internet-facing path removes the precondition for an unauthenticated attack and is the one control that takes effect immediately.
  4. Investigate the fabric, not only the host. Review orchestrator logs for requests that reached privileged functionality and for configuration changes that match no change record, compare edge device configurations and policies against a known-good baseline, check for new administrative users and API tokens, and rotate orchestrator credentials, certificates and edge activation secrets — a compromised VCO could have pushed changes that persist on the devices after the orchestrator is fixed.
  5. Validate input at the trust boundary as a standing practice. For services you operate, define server-side allowlists for format, type, length and range at every entry point, reject rather than repair non-conforming input, never let unvalidated data select which internal functionality is invoked, and keep privileged internal endpoints unreachable from the external interface by design rather than by filtering.

Technical Details

Arista describes CVE-2026-93952 as a security issue in on-premises VeloCloud Orchestrator that may allow a remote attacker to access privileged internal functionality and impact the VCO host, and NVD classifies the root as CWE-20, improper input validation. In that pattern, the product accepts data without verifying that it conforms to the expected constraints, and the unvalidated value then influences a decision it should not — here, which internal functionality a request reaches. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H states the exploitation conditions without any mitigating factor and, crucially, marks the scope as Changed: the resources impacted extend beyond the vulnerable component itself. For an SD-WAN orchestrator that assessment is accurate in the most literal way, because the component's whole function is to configure other devices; an attacker who controls it inherits a trusted channel to every edge node in the fabric and to the data describing them.

Frequently Asked Questions

Is CVE-2026-93952 being actively exploited?

Yes. CISA has added CVE-2026-93952 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the remediation deadline of September 25, 2026 has already passed. Use in ransomware campaigns is not recorded, and the EPSS score of 1.06% in the 64th percentile reflects a specialized target rather than mass scanning.

What products are affected by CVE-2026-93952?

CVE-2026-93952 affects on-premises Arista VeloCloud Orchestrator in versions 5.2.0 up to 5.2.3.16, 6.1.0 through 6.1.3.7, 6.4.0 up to 6.4.2.8 and 7.0.0 through 7.0.0.2. Hosted VCO instances, including Dedicated, were also impacted but have already been patched by Arista.

How do I fix CVE-2026-93952?

Upgrade on-premises VeloCloud Orchestrator to the fixed build for your branch, as listed in Arista Security Advisory 0183. Until the upgrade is complete, restrict access to the orchestrator to a dedicated management network, because the vulnerability requires no authentication. Afterwards, compare edge device configurations and policies against a known-good baseline and rotate orchestrator credentials, certificates and activation secrets.

How severe is CVE-2026-93952?

CVE-2026-93952 is rated Critical with a CVSS 3.1 base score of 10.0, the maximum on the scale: remote, unauthenticated access to privileged functionality with no user interaction, full impact on confidentiality, integrity and availability, and a changed scope because the consequences reach beyond the orchestrator itself. Its EPSS score of 1.06% is modest, but for an SD-WAN management plane the operational severity matches the numeric rating.

CVSS Score

10.0
CRITICAL(10.0)

EPSS Score

EPSS Score1.38%
EPSS Percentile72.7%

Dates

PublishedSeptember 22, 2026
Last ModifiedSeptember 23, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.