PYSEC-2026-34: Crawl4AI < 0.8.0 Docker API Local File Inclusion via file URL Handling
Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /executejs, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Crawl4AIto a version that resolves this vulnerability.Fixed in 0.8.0
Event History
Frequently Asked Questions
Which deployments are known to be affected?
The affected deployment type identified is the Crawl4AI Docker API deployment running a version earlier than 0.8.0. The provided information does not establish whether non-Docker deployments are affected.
Does exploitation require credentials or user interaction?
No. The vulnerability is exploitable remotely without authentication or user interaction when the relevant Docker API endpoints are exposed.
Which API routes are relevant for exposure assessment?
The affected routes are /execute_js, /screenshot, /pdf, and /html. They accept file:// URLs that can be used to request files from the server filesystem.
What version should be used to remediate the issue?
Upgrade Crawl4AI to version 0.8.0 or later. Versions prior to 0.8.0 are identified as affected.