# CVE-2026-91941: Crawl4AI before 0.9.3 Denial of Service via PDFContentScrapingStrategy

> Attackers can cause denial of service by forcing the library to download large PDFs without limits, exhausting system resources.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-35gf-m9jx-8qmx, GHSA-v2rm-hvrj-2x9q

## What is CVE-2026-91941?

CVE-2026-91941 is a high-severity denial of service vulnerability in unclecode crawl4ai, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-91941?


## How do I fix CVE-2026-91941?

No fix has been published for CVE-2026-91941 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91941 being exploited?

There is no known exploitation of CVE-2026-91941 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91941 and fix it if it is affected.

What it is: CVE-2026-91941 is a high-severity denial of service vulnerability in unclecode crawl4ai, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-91941 in the wild and no public exploit code.

Affected product: unclecode crawl4ai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91941/ (Markdown: https://insights.sbomify.com/CVE-2026-91941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91941
- OSV: https://osv.dev/vulnerability/CVE-2026-91941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91941/
Summaries are generated and may contain mistakes; the official description above is the record.