CVE-2026-26216

A critical remote code execution vulnerability exists in the Crawl4AI 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 attackers to import arbitrary modules and execute system commands.

Attack Vector:

POST /crawl
{
  "urls": ["https://example.com"],
  "hooks": {
    "code": {
      "on_page_context_created": "async def hook(page, context, **kwargs):\n    __import__('os').system('malicious_command')\n    return page"
    }
  }
}

Mitigation

1. Upgrade to v0.8.0 (recommended)
2. If unable to upgrade immediately:
   • Disable the Docker API
   • Block /crawl endpoint at network level
   • Add authentication to the API

Fix Details

1. Removed __import__ from allowed_builtins in hook_manager.py
2. Hooks disabled by default (CRAWL4AI_HOOKS_ENABLED=false)
3. Users must explicitly opt-in to enable hooks

Credits

Discovered by Neo by ProjectDiscovery (https://projectdiscovery.io)

An unauthenticated attacker can:

• Execute arbitrary system commands
• Read/write files on the server
• Exfiltrate sensitive data (environment variables, API keys)
• Pivot to internal network services
• Completely compromise the server

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Kodem intelligence

1. What is CVE-2026-26216? CVE-2026-26216 is a critical-severity code injection vulnerability in Crawl4AI (pip), affecting versions < 0.8.0. It is fixed in 0.8.0. Untrusted input is evaluated as executable code within the application's runtime environment.
2. Which versions of Crawl4AI are affected by CVE-2026-26216? Crawl4AI (pip) versions < 0.8.0 is affected.
3. Is there a fix for CVE-2026-26216? Yes. CVE-2026-26216 is fixed in 0.8.0. Upgrade to this version or later.
4. Is CVE-2026-26216 exploitable, and should I be worried? Whether CVE-2026-26216 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-26216 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-26216? Upgrade Crawl4AI to 0.8.0 or later.