CVE-2026-57572: Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args
Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browserconfig.extraargs, 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Crawl4AIto a version that resolves this vulnerability.Fixed in 0.9.0 - Compensating control
If you cannot upgrade immediately, ensure the Docker API server is not exposed unauthenticated (since the Docker API is unauthenticated by default); restrict network access to the Docker API to trusted sources only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-57572?
The severity of CVE-2026-57572 is critical, with a CVSS score of 10.
How do I fix CVE-2026-57572?
To fix CVE-2026-57572, upgrade to Crawl4AI version 0.9.0 or later.
What type of vulnerability is CVE-2026-57572?
CVE-2026-57572 is a code injection vulnerability that allows unauthenticated remote code execution.
What attack vector does CVE-2026-57572 exploit?
CVE-2026-57572 exploits the ability to send request-supplied launch arguments to the Chromium browser.
What could an attacker achieve by exploiting CVE-2026-57572?
An attacker could execute arbitrary commands on the server by injecting Chromium launch arguments through the vulnerable API.