Is CVE-2026-57572 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57572 being exploited in the wild.

How severe is CVE-2026-57572?

Critical severity, with a CVSS score of 10, published 6 July 2026.

Which products and versions are affected?

crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.0.

Is there a fix for CVE-2026-57572?

Yes. crawl4ai (PyPI): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-57572 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-57572?

Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57572: unclecode Crawl4AI remote code execution in Docker API server

CVE-2026-57572 · Severity: critical · CVSS 10 · Published 2026-07-06

Crawl4AI is an open-source tool used to crawl and scrape websites for use with Large Language Models (LLMs). A critical security flaw in its Docker API server allows an unauthenticated attacker to execute arbitrary commands on the underlying system. This could lead to a total compromise of the server, including the theft of sensitive data, access to environment secrets, and the ability to use the infrastructure for further attacks.

Technologies: crawl4ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-57572 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57572 being exploited in the wild.
How severe is CVE-2026-57572?: Critical severity, with a CVSS score of 10, published 6 July 2026.
Which products and versions are affected?: crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.0.
Is there a fix for CVE-2026-57572?: Yes. crawl4ai (PyPI): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57572 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-57572?: Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

crawl4ai (PyPI): upgrade to 0.9.0 or later
```
pip install "crawl4ai>=0.9.0"
```

Technical details

The vulnerability is an argument injection flaw (CWE-88) in the Docker API server's handling of the 'browser_config.extra_args' field. Because the API is unauthenticated by default, a remote attacker can send a crafted request to endpoints like /crawl or /crawl/stream containing malicious Chromium switches (such as --utility-cmd-prefix or --renderer-cmd-prefix) combined with --no-zygote. This causes the underlying Chromium process to execute attacker-controlled commands as the container's runtime user. While version 0.8.9 attempted to mitigate this with a denylist, it was incomplete; version 0.9.0 fixes the issue by establishing a proper trust boundary and rejecting requests that attempt to use these sensitive configuration fields.

Affected products

unclecode crawl4ai < 0.9.0

Identifiers

CVE-2026-57572
GHSA-r253-r9jw-qg44
PYSEC-2026-2139

Timeline

2026-06-18: patched: Version 0.9.0 released to address the RCE.
2026-07-06: disclosed: CVE-2026-57572 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.