PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-91941 – Denial of Service (Uncontrolled Resource Consumption) – Crawl4AI before 0.9.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-91941 is an uncontrolled resource consumption vulnerability (denial of service) affecting Crawl4AI, an open-source LLM-friendly web crawler and scraper, in versions prior to 0.9.3. The flaw resides in the PDFContentScrapingStrategy component used by Crawl4AI’s Docker API, allowing untrusted, unauthenticated clients to trigger resource exhaustion on the server. The vulnerability has a High severity rating (CVSS 8.7 / CVSS v3.1 7.5), with no authentication or user interaction required to exploit.

Technical details

  • Root cause: When PDFContentScrapingStrategy is selected, Crawl4AI downloads and processes a remote PDF specified by the client without enforcing any limit on file size, page count, or processing time.
  • Trigger conditions: An attacker submits a POST request to the Crawl4AI Docker API selecting the PDF scraping strategy and pointing it at a large or many-page remote PDF file.
  • Attack vector: Network-based, requires no privileges and no user interaction (CVSS AV:N/AC:L/PR:N/UI:N).
  • Impact: A single malicious request can exhaust disk space, CPU, and bandwidth on shared worker infrastructure, causing denial of service for the crawling service and any co-located workloads. The vulnerability affects availability only — no confidentiality or integrity impact is reported.

Affected software

  • Product: crawl4ai (PyPI package), maintained by unclecode
  • Vulnerable versions: All versions prior to 0.9.3
  • Fixed version: 0.9.3 and later

Severity

  • CVSS v4.0: 8.7 (High) — 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
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Crawl4AI to version 0.9.3 or later, which enforces limits on PDF size, page count, and processing time within PDFContentScrapingStrategy.
  • If immediate patching is not possible:
    • Disable or restrict access to the PDFContentScrapingStrategy option on any internet-facing Crawl4AI Docker API deployment.
    • Place rate limiting and request size restrictions in front of the Crawl4AI API to constrain the size and frequency of crawl requests.
    • Restrict API access to trusted/authenticated clients only, and monitor for abnormal disk, CPU, or bandwidth usage on worker instances handling PDF crawl requests.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge