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 Pro
CVE-2026-16812 Google Chronicle · YARA-L

Detect Arista VeloCloud Orchestrator On-Prem OS Command Injection (CVE-2026-16812) in Google Chronicle

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.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule velocloud_orchestrator_cmd_injection_cve_2026_16812 {
  meta:
    author = "df00tech detection engineering"
    description = "Detects OS command injection attempts against Arista VeloCloud Orchestrator On-Prem (CVE-2026-16812)"
    severity = "critical"
  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.target.url = /.*(\/portal|\/vco|\/velocloud|\/api).*/ nocase
    $http.target.url = /.*(;|&&|\||\$\(|`|wget%20|curl%20|%2Fbin%2Fsh|%2Fbin%2Fbash).*/ nocase
  match:
    $http over 5m
  condition:
    $http
}
critical severity medium confidence

Chronicle YARA-L rule flagging HTTP requests to Arista VeloCloud Orchestrator management paths that contain URL-encoded or raw shell metacharacters indicative of command injection exploitation attempts.

Data Sources

NETWORK_HTTP

Required Tables

NETWORK_HTTP

False Positives & Tuning

  • Authorized red team or vulnerability scanning activity using similar payloads
  • Legitimate API clients passing special characters in unrelated query parameters
  • Proxy rewriting that introduces encoded characters resembling injection tokens

Other platforms for 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.

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

  2. Test 2Spawn shell process from simulated web application parent

    Expected signal: Process creation event showing 'sh' or 'bash' with parent process name resembling 'java'.

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

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections