Quick answers
- Is CVE-2026-91941 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91941 being exploited in the wild.
- How severe is CVE-2026-91941?
- High severity, with a CVSS score of 7.5, published 15 September 2026.
- Which products and versions are affected?
- Crawl4AI Crawl4AI before 0.9.3.
- Is there a fix for CVE-2026-91941?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-91941 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-91941?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an uncontrolled resource consumption flaw (CWE-400) in the PDFContentScrapingStrategy component. Root cause: the strategy is included in the list of untrusted-allowed types, and the non-streaming crawl endpoint permits untrusted clients to select it. When invoked, the PDF processor streams remote PDFs to disk with no size cap (relying only on a never-enforced content-length header), and iterates through all pages without limits. The default Docker configuration ships with no per-request wall-clock deadline. Attack vector is network-based with no authentication required; an attacker sends a POST request targeting a large or high-page-count remote PDF. Impact is denial of service only (no data disclosure or code execution). The vulnerability is fixed in version 0.9.3.
Affected products
- Crawl4AI Crawl4AI before 0.9.3
Timeline
- 2026-08-31: disclosed: GitHub Security Advisory GHSA-v2rm-hvrj-2x9q published
- 2026-09-15: advisory: CVE-2026-91941 published on NVD