Detect Aquasecurity Trivy Embedded Malicious Code (CVE-2026-33634) in Sumo Logic CSE
CVE-2026-33634 describes an embedded malicious code vulnerability (CWE-506) in Aquasecurity Trivy, a widely-used open-source vulnerability scanner. A compromised or trojanized Trivy binary may execute attacker-controlled code during container image scanning, CI/CD pipeline runs, or Kubernetes admission checks. Because Trivy is frequently granted elevated permissions to access container registries, Kubernetes API servers, and cloud credential chains, a backdoored instance poses critical supply-chain risk: exfiltration of secrets, lateral movement into CI/CD infrastructure, and persistent implant installation. This detection monitors for anomalous process behavior, unexpected network egress, and suspicious file activity originating from Trivy processes.
MITRE ATT&CK
Sumo Detection Query
_sourceCategory=endpoint/process OR _sourceCategory=endpoint/network OR _sourceCategory=crowdstrike
| where process_name in ("trivy", "trivy-linux-amd64", "trivy-linux-arm64") or parent_process_name in ("trivy", "trivy-linux-amd64", "trivy-linux-arm64")
| eval is_suspicious_child = if(parent_process_name in ("trivy","trivy-linux-amd64","trivy-linux-arm64") and process_name in ("curl","wget","nc","python","python3","perl","ruby","bash","sh") and (matches(cmd_line, "(?i).*(base64|/dev/tcp|exec.*sh|reverse|implant).*") or matches(cmd_line, "(?i).*(wget|curl).+http")), "true", "false")
| eval is_suspicious_network = if(process_name in ("trivy","trivy-linux-amd64","trivy-linux-arm64") and !((dst_port in ("443","80")) and (matches(dst_host, "(?i).*(aquasecurity|ghcr\.io|github\.com).*"))), "true", "false")
| eval is_suspicious_file = if(process_name in ("trivy","trivy-linux-amd64","trivy-linux-arm64") and matches(file_path, "(?i).*(^/tmp/|/dev/shm/|/var/tmp/).*"), "true", "false")
| where is_suspicious_child = "true" or is_suspicious_network = "true" or is_suspicious_file = "true"
| count by host, user, process_name, cmd_line, parent_process_name, dst_host, dst_port, is_suspicious_child, is_suspicious_network, is_suspicious_file
| sort by _count descSumo Logic query correlating Trivy process anomalies: interpreter child spawns, egress to non-approved destinations, and temp directory writes that indicate CVE-2026-33634 embedded malicious code activation.
Data Sources
Required Tables
False Positives & Tuning
- Trivy DB mirror configurations pointing to internal artifact servers on non-standard ports
- Automated scan report pipelines using curl or wget as post-scan exporters
- Custom Trivy plugins writing temp artifacts before final report generation
- Dev/test environments running trivy against local registries with non-TLS connections
Other platforms for CVE-2026-33634
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 1Trivy Binary Hash Verification Failure Simulation
Expected signal: ProcessRollup or DeviceProcessEvents event for /tmp/trivy-test with a SHA-256 hash differing from the official trivy binary hash; file creation event for /tmp/trivy-test.
- Test 2Trivy Spawning Reverse Shell Child Process
Expected signal: ProcessRollup event showing trivy (or trivy-named process) as parent of nc/netcat; NetworkConnect event for local port 14444.
- Test 3Trivy Unexpected Outbound Network Connection
Expected signal: NetworkConnect event from a process named 'trivy' (via exec -a) to 169.254.169.254 port 80; DnsRequest or direct IP connection telemetry.
- Test 4Trivy Writing Dropper to Temp Directory
Expected signal: FileCreate event showing a trivy-named process writing an executable file to /dev/shm/; file hash and permissions captured in endpoint telemetry.
Unlock Pro Content
Get the full detection package for CVE-2026-33634 including response playbook, investigation guide, and atomic red team tests.