dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-26216

CRITICAL · 10.0 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 0.8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Crawl4AI versions prior to 0.8.0 in Docker API deployments contain an RCE vulnerability in the /crawl endpoint. The hooks parameter accepts Python code that is executed via exec() with __import__ included in the allowed builtins, enabling unauthenticated attackers to import arbitrary modules and execute system commands leading to full server compromise.

MitigationUpgrade to Crawl4AI 0.8.0 or later. If immediate patching is not feasible, restrict network access to the /crawl endpoint and implement authentication to prevent unauthenticated exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crawl4aiApplication
Affected:< 0.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Crawl4AI version
    Check the version of Crawl4AI running in your environment by querying the API version endpoint, checking the Docker container label, or reviewing your dependency configuration file
    Affected if The installed version is below 0.8.0
  2. Confirm Docker API deployment mode
    Determine if Crawl4AI is deployed with Docker API enabled - this is typically indicated by the DOCKER_API_ENABLED configuration flag or the presence of Docker socket mounting
    Affected if Docker API mode is enabled in the deployment configuration
  3. Check network exposure of Docker API
    Inspect network configuration to determine if the Docker API (usually port 2375/2376 or the Docker socket) is exposed to the network or accessible from untrusted sources
    Affected if The Docker API is exposed to networks that are not explicitly trusted
  4. Verify /crawl endpoint accessibility
    Test whether the /crawl endpoint is reachable without authentication - attempt a request to the endpoint or review access control configuration
    Affected if The /crawl endpoint is accessible without authentication from untrusted networks

You are affected if Crawl4AI version is below 0.8.0, Docker API deployment mode is enabled, and the /crawl endpoint or Docker API is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.8.0 or later
Fixed in 0.8.0
Interim mitigation

Upgrade to Crawl4AI 0.8.0 or later. If immediate patching is not feasible, restrict network access to the /crawl endpoint and implement authentication to prevent unauthenticated exploitation.

Recommended fix High confidence

0.8.0

  1. Stop the currently running Crawl4AI Docker container
  2. Pull the latest Crawl4AI image with version 0.8.0 or later: docker pull crawl4ai:latest or docker pull crawl4ai:0.8.0
  3. Remove the old container: docker rm <container_name>
  4. Deploy a new container using the updated image with appropriate environment variables and configurations
  5. Verify the container is running the fixed version
  6. Test that the /crawl endpoint no longer executes arbitrary code from the hooks parameter

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26216 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26216 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data