Arista VeloCloud Orchestrator Improper Input Validation (CVE-2026-93952)
Detects exploitation attempts and post-exploitation activity targeting CVE-2026-93952, an improper input validation vulnerability (CWE-20) in Arista VeloCloud Orchestrator (VCO). Listed in CISA KEV. The flaw permits attacker-supplied input to bypass validation on VCO management/API endpoints, enabling remote code execution or unauthorized command execution against the orchestrator. Detection focuses on anomalous requests to VCO API/admin paths, malformed input payloads reaching orchestrator endpoints, unexpected process spawning from the VCO web/application tier, and outbound connections from the orchestrator host.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Arista
- Product
- VeloCloud Orchestrator
Weakness (CWE)
Timeline
- Disclosed
- September 22, 2026
References & Proof of Concept
- https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-93952
- https://thehackernews.com/2026/09/new-cvss-100-velocloud-orchestrator.html
CVSS
What is CVE-2026-93952 Arista VeloCloud Orchestrator Improper Input Validation (CVE-2026-93952)?
Arista VeloCloud Orchestrator Improper Input Validation (CVE-2026-93952) (CVE-2026-93952) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Arista VeloCloud Orchestrator Improper Input Validation (CVE-2026-93952), covering the data sources and telemetry it touches: Web Proxy Logs, Network Security Appliance Logs, CommonSecurityLog. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
let vcoHosts = dynamic(["velocloud", "vco", "orchestrator"]);
let suspiciousPaths = dynamic(["/portal/", "/login/", "/api/", "/admin/", "/edge/"]);
CommonSecurityLog
| where DeviceVendor has_any ("Arista", "VeloCloud") or DestinationHostName has_any (vcoHosts)
| where RequestURL has_any (suspiciousPaths)
| where RequestMethod in ("POST", "PUT")
| where RequestURL matches regex @"(?i)(\.\.\/|%2e%2e|;|\||`|\$\(|<script|union\s+select|exec\s*\()"
or RequestContext matches regex @"(?i)(\.\.\/|%2e%2e|;|\||`|\$\()"
| project TimeGenerated, SourceIP, DestinationIP, DestinationHostName, RequestMethod, RequestURL, RequestContext, DeviceVendor
| summarize Count=count(), Paths=make_set(RequestURL, 20) by SourceIP, DestinationIP, DestinationHostName, bin(TimeGenerated, 10m)
| where Count >= 1 Identifies POST/PUT requests to Arista VeloCloud Orchestrator API/admin endpoints containing input-validation-bypass indicators (path traversal, command injection metacharacters, injection payloads) consistent with CVE-2026-93952 exploitation.
Data Sources
Required Tables
False Positives
- Legitimate administrators submitting complex configuration payloads that include special characters
- Automated VCO API integrations or CI/CD tooling posting structured JSON with escaped characters
- Vulnerability scanners and authorized penetration tests probing the orchestrator
Sigma rule & cross-platform mapping
The detection logic for Arista VeloCloud Orchestrator Improper Input Validation (CVE-2026-93952) (CVE-2026-93952) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: network_connection
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-93952
References (5)
- https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-93952
- https://thehackernews.com/2026/09/new-cvss-100-velocloud-orchestrator.html
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulated path traversal POST to VCO API endpoint
Expected signal: Proxy/web logs record a POST to /api/ with a ../ traversal token in the body.
- Test 2Simulated command-injection payload to VCO admin path
Expected signal: Web logs show a PUT to /admin/ containing $( and ; metacharacters.
- Test 3Post-exploitation shell spawn from application tier
Expected signal: EDR records bash/curl/wget spawned by the application service account with a download command line.
Response Playbook
Triage
- Confirm the destination host is an Arista VeloCloud Orchestrator instance and record its build/version against Arista Security Advisory 0183 to determine whether it is a patched release.
- Extract the full request URL and body from the alerting event and identify the specific input-validation-bypass pattern (path traversal, command injection metacharacters, script/SQL payload) that fired.
- Determine whether the source IP is an authorized administrator, known automation/scanner, or an unexpected external address; check for prior authentication or session context.
- Correlate the timestamp with orchestrator application/web logs and host process telemetry to see if any child process, file write, or outbound connection followed the request.
Containment
- If exploitation is confirmed or strongly suspected, isolate the VCO management interface — restrict access to a trusted admin allowlist via firewall/ACL and block the source IP.
- Apply the vendor fix per Arista Security Advisory 0183 (upgrade to the patched VeloCloud Orchestrator release) as prioritized under CISA BOD 26-04, or take the orchestrator offline if patching cannot be immediate.
- Rotate orchestrator administrative credentials, API tokens and any secrets reachable from the VCO host, and terminate active suspicious sessions.
Evidence Collection
- Preserve VCO web/application and access logs, the raw offending HTTP request/response, and any generated error or audit entries around the event window.
- Capture a forensic image or volatile-data snapshot (process list, network connections, recently modified files, cron/systemd persistence) of the orchestrator host before remediation.
Escalation Criteria
- ! Escalate to incident response immediately if a shell, download utility, or unexpected outbound connection is observed following the malformed request, indicating successful RCE.
- ! Escalate to management and consider regulatory/CISA notification if the orchestrator manages production SD-WAN edges and lateral movement, config tampering, or edge-device compromise is evident.
Investigation Guide
Forensic Artifacts
- >
VCO web/application server access and error logs showing the malformed POST/PUT request - >
New or modified files, cron/systemd units, or web-shell artifacts on the orchestrator host - >
Process execution records showing shell/download utilities spawned by the application service account
Tuning Guidance
Build a reference set of authorized administrator and automation source IPs and known scanner ranges, then exclude them from the alert to cut benign matches. Baseline the legitimate special characters that appear in valid VCO configuration payloads so the injection regex is tuned to genuine bypass attempts rather than escaped JSON. Once the orchestrator fleet is confirmed patched to the Advisory 0183 release, lower severity to informational for tracking while retaining the post-exploitation process correlation at high fidelity.
Hunting Queries
Surfaces source IPs generating high-volume or brute-force-style access to VeloCloud Orchestrator management endpoints, useful for spotting reconnaissance or exploitation attempts around CVE-2026-93952.
CommonSecurityLog | where DestinationHostName has_any ("velocloud","vco","orchestrator") | where RequestURL has_any ("/api/","/portal/","/admin/") | summarize Requests=count(), Methods=make_set(RequestMethod) by SourceIP, bin(TimeGenerated, 1h) | where Requests > 50 index=proxy (dest_host="*velocloud*" OR dest_host="*vco*") (url="*/api/*" OR url="*/admin/*") | stats count values(method) as methods by src_ip | where count > 50 Atomic Red Team Tests
Sends a POST request containing a path-traversal sequence to a lab VeloCloud Orchestrator API path to validate the improper-input-validation detection logic.
Command
curl -sk -X POST "https://vco.lab.local/api/edge/config" --data 'name=../../../../etc/passwd&val=test' -H 'Content-Type: application/x-www-form-urlencoded' Cleanup
echo 'No cleanup required; no server-side state created in lab.' Expected Telemetry
Proxy/web logs record a POST to /api/ with a ../ traversal token in the body.
Expected Detection
KQL/SPL rules fire on the path-traversal metacharacter in a POST to a VCO endpoint.
Submits a command-injection style payload to a lab orchestrator admin endpoint to exercise the metacharacter detection.
Command
curl -sk -X PUT "https://vco.lab.local/admin/settings" --data 'hostname=$(id);echo test' -H 'Content-Type: application/x-www-form-urlencoded' Cleanup
echo 'No cleanup required.' Expected Telemetry
Web logs show a PUT to /admin/ containing $( and ; metacharacters.
Expected Detection
Input-validation-bypass regex matches the injection metacharacters in the request.
Simulates a web/application service account spawning a shell that runs a download utility, mimicking successful RCE on the orchestrator host.
Command
sudo -u www-data /bin/bash -c 'curl -s http://127.0.0.1/healthz; wget -q http://127.0.0.1/beacon -O /tmp/beacon' Cleanup
rm -f /tmp/beacon Expected Telemetry
EDR records bash/curl/wget spawned by the application service account with a download command line.
Expected Detection
Elastic EQL sequence and CrowdStrike CQL fire on shell/download utility spawned by the web tier.