CVE-2026-57573 unclecode CVE debrief

Who should care

Users of Crawl4AI, especially those who expose the service to untrusted networks or users, should be aware of this vulnerability and take steps to mitigate it. This includes restricting access to trusted networks and users, monitoring for suspicious activity, and implementing additional security measures.

Technical summary

The Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed seed URLs straight to the crawler with no destination validation, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawler_config.stream=true with a URL pointing at an internal, private, or link-local address; the server fetched it and streamed the response body back. This issue is fixed in version 0.9.0.

Defensive priority

High

Recommended defensive actions

• Apply the patch from version 0.9.0
• Restrict access to the Crawl4AI service to trusted networks and users
• Monitor for suspicious activity
• Implement additional security measures such as IP blocking or rate limiting
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-06T21:16:58.197Z and was last modified on 2026-07-07T19:07:47.350Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus. Further verification is recommended to ensure accuracy.

Official resources