dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-26217

HIGH · 7.5 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 0.8.0 or later.
See remediation →
84/100
Remediation priority · High
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 local file inclusion vulnerability in the Docker API deployment. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.

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 before 0.8.0 in Docker API deployment have a local file inclusion vulnerability where the /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs without validation. This allows unauthenticated remote attackers to read arbitrary server files including /etc/passwd, /etc/shadow, config files, and /proc/self/environ to extract credentials and API keys.

MitigationUpgrade Crawl4AI Docker deployment to version 0.8.0 or later, which contains the fix for this LFI vulnerability. Additionally, implement input validation to reject file:// URL schemes at the API gateway or application layer.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 Crawl4AI version
    Check the installed Crawl4AI version by querying the API endpoint /version, checking the Docker image tag, or inspecting the package version if running from source. Compare against the affected range: versions before 0.8.0.
    Affected if The installed version is any version before 0.8.0
  2. Confirm Docker API deployment
    Determine whether the Crawl4AI instance is deployed using its Docker API configuration. Check if the application is running inside a Docker container and if the Docker API socket or port is accessible to the instance.
    Affected if The instance is deployed as a Docker API deployment and the vulnerable endpoints are network-accessible
  3. Verify affected endpoint exposure
    Identify whether the /execute_js, /screenshot, /pdf, and /html endpoints are exposed and accessible. These are the known endpoints that accept URL parameters.
    Affected if Any of these endpoints are accessible without additional authentication beyond the base API
  4. Test for file:// URL acceptance
    Send a test request with a file:// URL to one of the affected endpoints (for example, /html?url=file:///etc/passwd) to verify if the application accepts and processes file:// URL schemes without rejecting them.
    Affected if The application accepts file:// URLs and returns or attempts to read the referenced file content

The environment is affected if Crawl4AI version is before 0.8.0, deployed as a Docker API instance, and the /execute_js, /screenshot, /pdf, or /html endpoints are exposed and accept file:// URLs without validation.

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 Crawl4AI Docker deployment to version 0.8.0 or later, which contains the fix for this LFI vulnerability. Additionally, implement input validation to reject file:// URL schemes at the API gateway or application layer.

Recommended fix High confidence

0.8.0

  1. Pull the latest Crawl4ai Docker image with version 0.8.0 or later: docker pull crawl4ai:0.8.0
  2. Stop and remove the existing Crawl4ai container
  3. Deploy the new container using the same configuration parameters used for the previous version
  4. Verify the container is running: docker ps | grep crawl4ai
  5. Test that the /execute_js, /screenshot, /pdf, and /html endpoints no longer accept file:// URLs (these requests should be rejected or fail)

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

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26217 — 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-26217 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