CVE-2026-53753 IBM QRadar · QRadar

Detect Crawl4AI AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in IBM QRadar

Detects exploitation of CVE-2026-53753, a critical pre-authentication remote code execution vulnerability in Crawl4AI (<=0.8.6) Docker API. The vulnerability allows attackers to escape Python AST-based sandboxing via generator frame introspection (gi_frame.f_back chain), enabling arbitrary code execution without authentication. CVSS 9.8 critical; public PoC available.

MITRE ATT&CK

Tactic
Initial Access Execution Privilege Escalation

QRadar Detection Query

IBM QRadar (QRadar)
sql
SELECT DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') as EventTime,
  sourceip, destinationip, destinationport,
  URL, "username", QIDNAME(qid) as EventName,
  CATEGORYNAME(category) as Category
FROM events
WHERE (destinationport IN (11235, 8080, 8000)
  AND (URL ILIKE '%/execute%' OR URL ILIKE '%/run%' OR URL ILIKE '%/crawl%'))
AND LOGSOURCETYPENAME(devicetype) IN ('Linux OS', 'Docker', 'Nginx', 'Apache HTTP Server')
AND (payload ILIKE '%gi_frame%' OR payload ILIKE '%f_back%' OR payload ILIKE '%__globals__%'
  OR payload ILIKE '%__builtins__%' OR payload ILIKE '%os.system%' OR payload ILIKE '%__import__%')
LAST 24 HOURS
critical severity medium confidence

QRadar AQL query to detect inbound HTTP requests to Crawl4AI endpoints combined with payload patterns indicating AST sandbox escape exploitation of CVE-2026-53753.

Data Sources

QRadar Network ActivityLinux OS log sourceDocker log sourceWeb server logs

Required Tables

events

False Positives & Tuning

  • Legitimate web scraping services using Crawl4AI with dynamic code features
  • Penetration testing activity against internally deployed Crawl4AI instances
  • Debug-mode Python applications that expose frame introspection in logs
  • Log aggregation pipelines that include raw Python tracebacks referencing frame attributes

Other platforms for CVE-2026-53753


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 1CVE-2026-53753 Basic Sandbox Escape via gi_frame

    Expected signal: HTTP POST to /execute endpoint followed by Python process executing os.system('id') and writing to /tmp/crawl4ai_pwned.txt; child process of uvicorn/gunicorn spawning /bin/sh

  2. Test 2CVE-2026-53753 Remote Code Execution with Reverse Shell

    Expected signal: Outbound TCP connection from Crawl4AI container to attacker IP on port 4444; subprocess.Popen spawning bash with stdin redirected to network socket

  3. Test 3CVE-2026-53753 Credential Exfiltration from Container Environment

    Expected signal: HTTP POST with gi_frame payload followed by Python reading os.environ; response containing environment variable key-value pairs potentially including API_KEY, DATABASE_URL, VAULT_TOKEN

  4. Test 4CVE-2026-53753 Unauthenticated Version Fingerprinting

    Expected signal: Unauthenticated HTTP GET to /health or root endpoint returning Crawl4AI version information without requiring credentials

Unlock Pro Content

Get the full detection package for CVE-2026-53753 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections