CVE-2026-26216: Crawl4AI Docker API Unauthenticated Remote Code Execution via Hooks Parameter
Crawl4AI versions before 0.8.0 with the Docker API deployment can execute code supplied in the hooks parameter of the /crawl endpoint, according to the record. The record describes unauthenticated remote code execution with a CVSS base score of 10 and CWE-94 (Code Injection). No confirmed exploitation appears in the sources consulted, and the CISA KEV catalog does not list this CVE.
Overview
The record describes a remote code execution issue in the Docker API deployment of Crawl4AI. The /crawl endpoint accepts a hooks parameter, which the record says contains Python code executed with exec(). The __import__ builtin was among the allowed builtins, which the record identifies as the enabling condition.
Impact
- The record states that an unauthenticated remote attacker can import arbitrary modules and execute system commands.
- The record lists possible consequences: full server compromise, file read and write access, sensitive data exfiltration and lateral movement inside internal networks.
- CVSS base score 10 is recorded by VulnCheck and in the other scores listed. The weakness is classified as CWE-94 (Code Injection).
Affected products and versions
- Kidocode Crawl4ai: versions before 0.8.0.
- Unclecode Crawl4ai: versions before 0.8.0.
- The allowed reference version in the record is 0.8.0. The record does not state explicitly which build contains the fix, so the boundary is taken from the affected range.
Exploitation status
- The CISA KEV catalog does not list this CVE in the record, so no active exploitation is stated.
- No confirmed exploitation appears in the sources consulted.
- The SSVC data in the record reports exploitation as none and automatable as yes. The EPSS probability is 0.06001 with percentile 0.93311, as recorded.
Remediation and mitigation
- Upgrade Crawl4ai deployments to version 0.8.0 or later, as the affected range ends at that version.
- Review the vendor advisory listed in the record, which is classified as a mitigation, for the vendor's guidance.
- Until patching is complete, limit network exposure of the Docker API, restrict access to trusted networks and place the service behind authentication controls.
- Check whether the hooks feature is required in your environment and disable unused functionality where possible.
Detection guidance
- Review access logs of the /crawl endpoint for unexpected or unknown requests, especially requests carrying a hooks parameter from untrusted sources.
- Monitor the Crawl4ai host for unexpected child processes, new files or unusual outbound connections originating from the service account.
- Correlate application events with network telemetry to identify possible lateral movement.
Limitations of the available information
- The record does not provide exploit details, proof of concept material or the full text of the vendor advisory.
- The record does not state the exact fixed build or the precise code change.
- The record contains an EPSS date of 2026-10-23, which is later than the published date; this has not been independently verified.
- Whether any deployment has been compromised is unknown from the sources consulted.
Frequently asked questions
Which Crawl4AI versions are affected?
According to the record, Kidocode Crawl4ai and Unclecode Crawl4ai versions before 0.8.0 are affected.
Is this vulnerability being actively exploited?
The CISA KEV catalog does not list this CVE in the record, and no confirmed exploitation appears in the sources consulted.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.