Detect Crawl4AI Docker API Multiple Critical Vulnerabilities (File Write, SSRF, Auth Bypass, XSS, JS Execution) in Sumo Logic CSE
Detects exploitation of CVE-2026-56266 affecting Crawl4AI <= 0.8.6 Docker API. The vulnerability bundle includes unauthenticated access (CWE-306), path traversal file write (CWE-22), server-side request forgery (CWE-918), stored/reflected XSS (CWE-79), JavaScript injection/execution (CWE-94), and hardcoded credentials (CWE-798). A public PoC is available. Successful exploitation allows full container compromise, internal network pivoting, and arbitrary file write to the host.
MITRE ATT&CK
Sumo Detection Query
_sourceCategory=web/access OR _sourceCategory=proxy/logs OR _sourceCategory=nginx/access
| parse regex "(?<src_ip>\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}) .+ \"(?<method>\w+) (?<uri>[^\"]+) HTTP/[\d.]+\" (?<status>\d{3})"
| where status matches "[0-9]*"
| where uri matches "*/crawl*" OR uri matches "*/execute_js*" OR uri matches "*/screenshot*" OR uri matches "*/extract*"
| if (uri matches "*../*" OR uri matches "*%2e%2e*" OR uri matches "*%252e*", "PathTraversal",
if (uri matches "*169.254.169.254*", "SSRF-CloudMetadata",
if (uri matches "*file://*" OR uri matches "*gopher://*", "SSRF-AltScheme",
if (uri matches "*127.0.0.1*" OR uri matches "*localhost*", "SSRF-Loopback",
if (uri matches "*execute_js*", "JSCodeExecution",
if (uri matches "*<script*" OR uri matches "*javascript:*", "XSS",
if (uri matches "*192.168.*" OR uri matches "*10.*", "SSRF-PrivateRange", "SuspiciousAPICall"))))))) as threat_type
| count by src_ip, threat_type, uri
| where _count >= 1
| sort by _count descSumo Logic query parsing web access logs to identify Crawl4AI API exploitation patterns including path traversal, SSRF variants, JavaScript injection, and XSS attempts.
Data Sources
Required Tables
False Positives & Tuning
- Security testing frameworks (nuclei, wfuzz) running authorized scans against Crawl4AI
- Legitimate crawl jobs that include URLs with IP addresses in private ranges as crawl targets
- Development teams testing JavaScript execution features during sprint cycles
- CDN or WAF test probes that generate unusual URI patterns in access logs
Other platforms for CVE-2026-56266
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 1Crawl4AI Unauthenticated API Access Test
Expected signal: HTTP POST to port 11235 /crawl endpoint with 200 response and no Authorization header in request logs
- Test 2Crawl4AI SSRF via Cloud Metadata Endpoint
Expected signal: Outbound HTTP connection from Crawl4AI container to 169.254.169.254:80; logged in container network flow data and potentially in WAF/proxy logs
- Test 3Crawl4AI Path Traversal File Read via Screenshot Endpoint
Expected signal: HTTP POST to /screenshot or /crawl with file:// URL scheme in request body; response may contain file contents if vulnerable
- Test 4Crawl4AI JavaScript Code Injection via execute_js Endpoint
Expected signal: HTTP POST to /execute_js with js_code parameter containing JavaScript; Crawl4AI process spawning Playwright browser subprocess
Unlock Pro Content
Get the full detection package for CVE-2026-56266 including response playbook, investigation guide, and atomic red team tests.