dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-56260

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-12
Fix available
A fix is available. Upgrade to 0.8.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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 before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.

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 before version 0.8.7 has an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing authenticated attackers to use path traversal sequences or absolute paths to write files to any location writable by the application's user, leading to potential server compromise and denial of service.

MitigationUpgrade to Crawl4AI version 0.8.7 or later which contains the fix. As a compensating control, implement strict input validation on the output_path parameter to reject path traversal sequences and restrict write locations to allowed directories.

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.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
    Locate the Crawl4AI installation and retrieve its version number (e.g., check package.json, setup.py, pip show, or the application's /version endpoint if available). Compare this version against the affected range: versions prior to 0.8.7 are vulnerable.
    Affected if Installed version is lower than 0.8.7
  2. Confirm Docker API server is enabled
    Examine the Crawl4AI configuration files or startup parameters for settings related to the Docker API server. Look for flags such as --docker-api, --enable-docker-api, or similar configuration that enables the built-in Docker API server functionality.
    Affected if Docker API server feature is enabled and running
  3. Verify /screenshot and /pdf endpoints are accessible
    Check if the Docker API server's REST endpoints /screenshot and /pdf are exposed. This may be configurable via a web server, reverse proxy, or the application itself. Attempt a local request to these endpoints or inspect routing/configuration to determine accessibility.
    Affected if The /screenshot or /pdf endpoints are reachable (locally or remotely)
  4. Inspect output_path parameter handling
    Review the source code or configuration of the /screenshot and /pdf endpoint handlers. Look for input validation logic applied to the output_path parameter. Specifically check if path traversal sequences (..) or absolute paths are validated or blocked before file write operations.
    Affected if No validation exists on output_path, or validation can be bypassed

You are affected if running Crawl4AI version below 0.8.7 with the Docker API server and its /screenshot or /pdf endpoints enabled, and the output_path parameter lacks proper path validation to prevent traversal or absolute path writes.

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.7 or later
Fixed in 0.8.7
Interim mitigation

Upgrade to Crawl4AI version 0.8.7 or later which contains the fix. As a compensating control, implement strict input validation on the output_path parameter to reject path traversal sequences and restrict write locations to allowed directories.

Recommended fix High confidence

0.8.7 or later

  1. Upgrade Crawl4ai to version 0.8.7 or later to obtain the fixed release
  2. Verify the installation was successful by checking the installed version
  3. Test that the /screenshot and /pdf endpoints now properly validate the output_path parameter and reject path traversal attempts
  4. Ensure any automated systems or scripts that interact with these endpoints are updated to use the validated API

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

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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