Live › vulnerability › CVE-2026-119119
Crawl4AI's Docker API server does not cap the delay_before_return_html, mean_delay and max_range fields in crawl requests. An unauthenticated attacker can send very large values to /crawl or /crawl/stream to hold browser pages and stall the rate limiter, blocking other crawls.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:25 UTC. All times on this page are UTC.
Teams running the Crawl4AI Docker API server that accept crawl requests from networks they do not fully control. Library-only use without the Docker API server is not described as exposed. Deployments behind authentication or limited to trusted internal callers are less exposed, though the sources do not say whether authentication is enforced by default.
No product ranges from the sources yet.
pip show crawl4ai or the image tag of the Docker deployment./crawl and /crawl/stream endpoints.0.9.5 are affected; move to 0.9.5 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Crawl4AI before 0.9.5 contains a denial of service vulnerability in the Docker API server where _clamp_untrusted() fails to cap the delay_before_return_html, mean_delay, and max_range fields of untrusted CrawlerRunConfig bodies. Unauthenticated attackers can send huge values to /crawl or /crawl/stream to hold browser pages or stall the rate limiter, exhausting the page pool and blocking other crawls.
This page as .md · .json · in your agent: get_signal("CVE-2026-119119")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.