GPU VulnDB

Database/AI/ML frameworks & serving

Crawl4AI: request-supplied Chromium switches give command execution in the crawler container

CVSS 10.0CVE-2026-57572AI/ML frameworks & servingcurated

Impact

The Docker API server accepted browser_config.extra_args from the request and passed it into Chromium's launch arguments. An attacker can inject switches that replace a child-process launch command and combine them with --no-zygote, making Chromium exec an attacker-chosen command as the container's runtime user. The API ships unauthenticated by default, so a single HTTP request is the whole exploit. On a fleet this container usually sits inside the cluster network with the crawl targets, output storage and whatever provider keys the retrieval pipeline needs, so the payoff is a foothold plus the credentials mounted next to it.

Who can reach it

Anyone who can reach the Crawl4AI Docker API port. Unauthenticated in the default deployment; an in-cluster pod or anything on the same network segment is enough, and no browser interaction is required.

What to do

Upgrade to 0.9.0 and redeploy the container. Until then, put authentication or a network policy in front of the API port and reject client-supplied browser_config.extra_args at the proxy. Container image bump and restart - no node-level maintenance.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.