Quick answers
- Is CVE-2026-26216 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26216 being exploited in the wild.
- How severe is CVE-2026-26216?
- Critical severity, with a CVSS score of 10, published 12 February 2026.
- Which products and versions are affected?
- crawl4ai (PyPI) < 0.8.0, ECOSYSTEM:introduced=0,fixed=0.8.0.
- Is there a fix for CVE-2026-26216?
- Yes. crawl4ai (PyPI): upgrade to 0.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-26216 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-26216?
- Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- crawl4ai (PyPI): upgrade to 0.8.0 or later
pip install "crawl4ai>=0.8.0"
Technical details
A remote code execution (RCE) vulnerability exists in the /crawl endpoint of Crawl4AI's Docker API deployment. The endpoint accepts a 'hooks' parameter containing Python code that is processed using the exec() function. While a sandbox was intended, the '__import__' builtin was explicitly allowed, enabling unauthenticated attackers to import the 'os' module and execute arbitrary system commands. This is classified as a code injection vulnerability (CWE-94). The issue is resolved in version 0.8.0 by removing '__import__' from the allowed builtins and disabling hooks by default via the CRAWL4AI_HOOKS_ENABLED environment variable.
Affected products
- unclecode Crawl4AI < 0.8.0
Identifiers
- CVE-2026-26216
- GHSA-5882-5rx9-xgxp
- PYSEC-2026-33
Timeline
- 2026-01-16: advisory: Vendor security advisory published on GitHub
- 2026-02-12: disclosed: CVE-2026-26216 published