PYPI · JANUARY 2026 · EARLY WARNING

Crawl4AI Docker API Vulnerable to Remote Code Execution

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-5882-5RX9-XGXPSeverity: HIGH

An early warning has been issued regarding a critical remote code execution vulnerability in the Crawl4AI Docker API deployment. Users of the crawl4ai (pypi) package are reportedly affected.

What happened

According to the GitHub Advisory Database, the Crawl4AI Docker API appears to be vulnerable to remote code execution via the `/crawl` endpoint. This endpoint accepts a `hooks` parameter containing Python code that is executed using `exec()`. The `__import__` builtin was included in the allowed builtins, allowing attackers to import arbitrary modules and execute system commands.

To assess your exposure, check if you are using the crawl4ai (pypi) package in your projects. If so, it is recommended to upgrade to version 0.8.0 as soon as possible. Alternatively, you can disable the Docker API and block the `/crawl` endpoint at the network level to mitigate the risk.

This vulnerability is under investigation, and further details may emerge. For the latest information, consult the primary sources linked in the advisory.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If crawl4ai is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats