CVE-2026-57572
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCrawl4AI 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCrawl4AI versions prior to 0.9.0 have a command injection vulnerability in the Docker API server where user-supplied browser_config.extra_args are passed directly to Chromium launch arguments. By injecting Chromium switches (e.g., --no-zygote combined with child-process replacement), attackers can achieve arbitrary command execution as the container's runtime user. The unauthenticated Docker API enables remote code execution with a single HTTP request.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Crawl4AI Docker API is accessibleCheck if the Docker API port (commonly 8555 or 8844) used by Crawl4AI is listening and reachable on your network interfaces. Use 'netstat' or 'ss' to list open ports and identify if the Crawl4AI service port is exposed.Affected if The Docker API port is open and accessible to your network.
-
Determine installed Crawl4AI versionQuery the Crawl4AI service version endpoint or inspect the running container image tag. You can use 'docker ps' to find the container and 'docker inspect <container_id>' to retrieve the image information, then compare the version to 0.9.0.Affected if The running Crawl4AI version is earlier than 0.9.0.
-
Verify Docker API is unauthenticatedTest if HTTP requests to the Crawl4AI Docker API endpoint can be made without providing any authentication credentials. Attempt an unauthenticated request to the API to confirm accessibility.Affected if The Docker API accepts requests without authentication.
-
Check for exposed Docker API to untrusted networksReview your network firewall rules and container runtime configuration to determine if the Docker API is bound to an IP address accessible from untrusted networks (such as 0.0.0.0 or a public-facing interface).Affected if The Docker API is bound to a public or untrusted network interface.
Your environment is affected if you are running Crawl4AI versions prior to 0.9.0 with the Docker API accessible and unauthenticated, allowing remote attackers to inject Chromium arguments for command execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.9.0
Upgrade to Crawl4AI version 0.9.0 or later. Additionally, ensure the Docker API is not exposed to untrusted networks and consider implementing authentication if exposure is required.
0.9.0
- Upgrade Crawl4ai to version 0.9.0 or later to remediate the vulnerability
- If using Docker, pull the updated image (e.g., docker pull crawl4ai:latest or specific version tag for 0.9.0)
- Restart the Crawl4ai service with the new image
- Verify the installation by checking the version: docker run crawl4ai --version or equivalent
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57572 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data