dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-56261

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 0.8.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 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 a server-side request forgery (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints, which accept webhook URLs without destination validation. An attacker can supply webhook URLs pointing to private or internal IP ranges, Docker networks, or cloud metadata endpoints (e.g. 169.254.169.254), causing the server to make requests to internal services and potentially expose cloud metadata.

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 SSRF vulnerability in its Docker API server where the /crawl/job and /llm/job endpoints accept webhook URLs without validating the destination. This allows attackers to supply URLs pointing to private/internal IP ranges, Docker networks, or cloud metadata services (169.254.169.254), causing the server to make requests to internal resources and potentially expose sensitive cloud metadata.

MitigationImplement strict webhook URL validation that blocks requests to private IP ranges (RFC 1918), loopback addresses, link-local addresses, Docker networks, and cloud metadata endpoints (169.254.169.254). Use an allowlist approach for permitted webhook destinations.

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
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 installation and version
    Check the installed Crawl4AI version by reviewing the Docker container image tag, package.json, or running 'pip show crawl4ai' if installed as a Python package. Compare against version 0.8.7.
    Affected if Version is below 0.8.7 or version cannot be determined (indicating outdated installation)
  2. Verify Docker API server is running
    Confirm the Crawl4AI Docker container or service is active and listening on its API port (typically 8000 or 8080). Check running processes or Docker container status.
    Affected if The Docker API server is exposed and accessible to the network or untrusted users
  3. Inspect /crawl/job and /llm/job endpoint accessibility
    Attempt to access or probe the /crawl/job and /llm/job REST endpoints (e.g., curl http://<server>:<port>/crawl/job) to confirm they respond without authentication or authorization controls.
    Affected if These endpoints are reachable without authentication and accept webhook URL parameters
  4. Check for webhook URL validation in configuration
    Review Crawl4AI configuration files, environment variables, or API settings for any webhook URL validation rules. Look for settings related to URL allowlisting, IP range blocking, or metadata endpoint protection.
    Affected if No webhook URL validation is configured, or validation does not block private IP ranges (RFC 1918), loopback (127.0.0.0/8), link-local (169.254.0.0/16), Docker networks, or cloud metadata endpoints (169.254.169.254)
  5. Confirm network exposure of the API server
    Determine if the Crawl4AI API server is bound to 0.0.0.0 (all interfaces) rather than localhost only, or if firewall rules permit external access to the API port.
    Affected if The API server is accessible from untrusted networks or the internet

You are affected if running Crawl4AI/Kidocode version below 0.8.7 with the Docker API server endpoints /crawl/job or /llm/job exposed and webhooks can be configured without IP range 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.7 or later
Fixed in 0.8.7
Interim mitigation

Implement strict webhook URL validation that blocks requests to private IP ranges (RFC 1918), loopback addresses, link-local addresses, Docker networks, and cloud metadata endpoints (169.254.169.254). Use an allowlist approach for permitted webhook destinations.

Recommended fix High confidence

0.8.7

  1. Pull the latest Crawl4ai Docker image version 0.8.7 or later: docker pull crawl4ai:0.8.7
  2. Redeploy the Crawl4ai container using the updated image
  3. Verify the installed version by checking the container tag or querying the API version endpoint

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

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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