Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-16812.
Upgrade to ProArista VeloCloud Orchestrator On-Prem OS Command Injection (CVE-2026-16812)
Detects exploitation attempts and post-exploitation indicators of CVE-2026-16812, an OS command injection vulnerability (CWE-78) in Arista VeloCloud Orchestrator On-Prem, actively exploited in the wild and listed on CISA KEV. Attackers send crafted HTTP requests to the Orchestrator management application that result in arbitrary OS command execution on the underlying host, typically leading to shell spawning, reverse shell callbacks, credential harvesting, or webshell deployment.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Arista
- Product
- VeloCloud Orchestrator
Weakness (CWE)
Timeline
- Disclosed
- July 27, 2026
References & Proof of Concept
- https://www.arista.com/en/support/advisories-notices/security-advisory/24364-security-advisory-0144
- 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-16812
CVSS
CVSS: Not yet rated
What is CVE-2026-16812 Arista VeloCloud Orchestrator On-Prem OS Command Injection (CVE-2026-16812)?
Arista VeloCloud Orchestrator On-Prem OS Command Injection (CVE-2026-16812) (CVE-2026-16812) 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 On-Prem OS Command Injection (CVE-2026-16812), covering the data sources and telemetry it touches: CommonSecurityLog, VMConnection, Syslog. 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 SuspiciousTokens = dynamic(['; ','&&','|','$(','`','wget ','curl ','/bin/sh','/bin/bash','base64 -d','python -c','nc -e','chmod +x']);
union isfuzzy=true
(CommonSecurityLog
| where DeviceVendor has 'Arista' or DeviceProduct has 'VeloCloud'
| where RequestURL has_any ('/portal', '/vco', '/velocloud', '/api')
| extend DecodedUrl = url_decode(RequestURL)
| where DecodedUrl has_any (SuspiciousTokens)),
(VMConnection
| where ProcessName has_any ('sh','bash','python','curl','wget','nc')
| where ParentProcessName has_any ('java','node','tomcat','httpd','nginx'))
| project TimeGenerated, DeviceVendor, SourceIP, DestinationIP, RequestURL, ProcessName, ParentProcessName
| sort by TimeGenerated desc Detects HTTP requests to Arista VeloCloud Orchestrator management endpoints containing shell metacharacters or command-injection payload tokens, and correlates with unexpected child processes spawned from the Orchestrator's web application service (Java/Tomcat).
Data Sources
Required Tables
False Positives
- Legitimate administrative scripts uploading configuration via automation using pipe or ampersand characters in benign contexts
- Vulnerability scanners intentionally sending injection test payloads without malicious follow-up
- Third-party network monitoring appliances proxying requests through the same reverse proxy path patterns
Sigma rule & cross-platform mapping
The detection logic for Arista VeloCloud Orchestrator On-Prem OS Command Injection (CVE-2026-16812) (CVE-2026-16812) 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:
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-16812
References (4)
- https://www.arista.com/en/support/advisories-notices/security-advisory/24364-security-advisory-0144
- 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-16812
Testing Methodology
Validate this detection against 4 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 1Simulate command injection payload via crafted HTTP request
Expected signal: Web/proxy access log entry showing the crafted URI with embedded semicolon and 'id' command token.
- Test 2Spawn shell process from simulated web application parent
Expected signal: Process creation event showing 'sh' or 'bash' with parent process name resembling 'java'.
- Test 3Simulate outbound tool download via curl/wget
Expected signal: Process execution log for curl/wget plus outbound network connection to the lab test server.
- Test 4Drop and remove a test webshell-like file
Expected signal: File creation and deletion event under the simulated web application directory captured by EDR/FIM.
Unlock playbooks & atomic tests with Pro
Get the full detection package for CVE-2026-16812 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month