CVE-2026-26216: Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter
Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
Security readout for executives and security teams
Plain-English summary
CVE-2026-26216 is a critical unauthenticated remote code execution issue in Crawl4AI Docker API deployments before 0.8.0. A public or internal exposed /crawl API could let an attacker run code on the server. Successful compromise could expose files, secrets, and connected internal systems.
Executive priority
Treat as urgent for any exposed Crawl4AI Docker API. Prioritize upgrade and exposure reduction because exploitation could move directly from unauthenticated API access to server compromise.
Technical view
The /crawl endpoint accepts a hooks parameter containing Python code executed with exec(). The allowed builtins included __import__, enabling module import and command execution without authentication. The issue is classified as CWE-94 with CVSS 4.0 score 10.0 for Crawl4AI Docker API deployments before 0.8.0.
Likely exposure
Organizations are exposed if they run Crawl4AI before 0.8.0 in Docker API mode, especially where the API is reachable from the internet or broad internal networks.
Exploitation context
The source bundle does not cite CISA KEV listing or confirmed active exploitation. However, the vulnerability is network reachable, unauthenticated, low complexity, and can provide full server compromise when exposed.
Researcher notes
Evidence is strongest for the vulnerable code path and version boundary from the provided advisories. No source in the bundle confirms exploitation in the wild. Validate exposure by deployment mode, version, API reachability, and authentication controls.
Mitigation direction
Upgrade Crawl4AI Docker API deployments to version 0.8.0 or later.
Follow the GitHub advisory and v0.8.0 release notes for vendor-specific remediation details.
Remove unauthenticated external access to the Docker API while remediation is pending.
Limit API reachability to trusted networks and authenticated callers where operationally possible.
Validation and detection
Inventory Crawl4AI deployments and identify Docker API instances below version 0.8.0.
Confirm whether the /crawl endpoint is reachable from untrusted networks.
Review API logs for unexpected hooks parameter usage or suspicious crawl requests.
Check affected hosts for signs of file access, command execution, or credential exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.