CVE-2026-26216: Kidocode Crawl4ai remote code execution (CVSS 10.0)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Kidocode Crawl4ai< 0.8.0

Remediation

Fixed in

Kidocode Crawl4ai≥ 0.8.0

Patch & vendor advisories

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-5882-5rx9-xgxp

References

https://github.com/unclecode/crawl4ai/blob/main/docs/blog/release-v0.8.0.mdRelease Notes
https://github.com/unclecode/crawl4ai/security/advisories/GHSA-5882-5rx9-xgxpMitigationVendor Advisory
https://www.vulncheck.com/advisories/crawl4ai-docker-api-unauthenticated-remote-code-execution-via-hooks-parameterThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-26216 being actively exploited?

CVE-2026-26216 is not in the CISA KEV catalog. Its EPSS exploit probability is 6.00%.

How severe is CVE-2026-26216?

CVE-2026-26216 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 6.00% probability of exploitation.

Which products are affected by CVE-2026-26216?

Affected products include Kidocode Crawl4ai.

How do I fix CVE-2026-26216?

Upgrade affected software to a fixed version, for example Kidocode Crawl4ai 0.8.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-26216 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo