CVE-2026-26216: Crawl4AI is Vulnerable to Remote Code Execution in Docker API via Hooks Parameter

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 6.0%, percentile 93: FIRST’s model estimates a 6.0% chance of exploitation activity in the next 30 days, higher than 93% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes Crawl4AI (PyPI) < 0.8.0, fixed in 0.8.0. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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:

Impact

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

Mitigation

Weakness type: CWE-94.

Product: Crawl4AI (PyPI) · Assigned by: VulnCheck · Published: 2026-02-12

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 6.00% probability of exploitation activity in the next 30 days; percentile 93.

Timeline

• 2026-01-16 — GitHub-reviewed advisory GHSA-5882-5rx9-xgxp published (critical)
• 2026-02-12 — CVE record published by VulnCheck
• 2026-10-08 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. github.com github.com
2. github.com github.com

Vulnerability records

1. GitHub Advisory GHSA-5882-5rx9-xgxp github.com
2. CVE.org record CVE-2026-26216 cve.org
3. NVD entry CVE-2026-26216 nvd.nist.gov

Other references from the CVE record and advisory

1. vulncheck.com vulncheck.com
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical PyPI advisories · Today’s Security Digest