Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/unclecode/crawl4ai/commit/60886d1a0c52682e4c83a7cef9dfac417fff6bd2 Patch
- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-r253-r9jw-qg44 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 10.0 · kidocodeNVD modified 2026-10-25 20:10
Affected (CPE criteria) 1
cpe:2.3:a:kidocode:crawl4ai:*:*:*:*:*:*:*:*