CVE-2026-91941
nicheDenial of Service in Crawl4AI PDF Scraping Strategy (before 0.9.3)
Crawl4AI versions before 0.9.3 contain an uncontrolled resource consumption flaw (CWE-400) in the PDFContentScrapingStrategy component. An unauthenticated attacker can send a POST request that selects the PDF scraping strategy and points it at an arbitrarily large remote PDF, which the server downloads and processes without any file-size or page-count limits. This exhausts disk space, CPU, and bandwidth on the worker, causing denial of service for shared or multi-tenant Crawl4AI deployments that accept untrusted crawl requests. The issue is rated high severity (CVSS 4.0: 8.7) because it requires no privileges or user interaction and has a full availability impact. No public proof of concept is known, it is not in the CISA KEV catalog, and there is no evidence of in-the-wild exploitation.
What to do: Upgrade Crawl4AI to version 0.9.3 or later, which introduces size and page limits for the PDF scraping strategy. Until patched, restrict API access to authenticated or trusted networks, and disable or block the PDFContentScrapingStrategy for untrusted requests. Consider enforcing proxy-level download size caps and timeouts, and monitor workers for abnormal disk, CPU, or bandwidth consumption as signs of abuse.
| Crawl4AI | before 0.9.3 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Crawl4AI before 0.9.3 contains an uncontrolled resource consumption vulnerability in PDFContentScrapingStrategy that allows untrusted clients to cause denial of service. Attackers can select the PDF scraping strategy in POST requests to download large remote PDFs without size or page limits, exhausting disk, CPU, and bandwidth on shared workers.
- Weakness
- CWE-400
- Vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.