dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-53754

HIGH · 7.5 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 0.8.8 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 is an open-source LLM friendly web crawler & scraper. Prior to 0.8.8, the Docker API server's SSRF protection (validate_webhook_url / validate_url_destination in deploy/docker/utils.py) used an explicit IPv4/IPv6 CIDR blocklist that missed several address families. An attacker could reach internal services and cloud metadata endpoints (e.g. 169.254.169.254) despite the filter by encoding an internal IPv4 address inside an IPv6 transition form, or by using the IPv6 unspecified address. Because the Docker API is unauthenticated by default (jwt_enabled: false), no credentials are required. This vulnerability is fixed in 0.8.8.

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.8 have an SSRF vulnerability in the Docker API server's URL validation functions. The blocklist only covers a subset of IPv4/IPv6 address families, failing to block internal IPv4 addresses encoded as IPv6 transition formats (e.g., ::ffff:10.x.x.x) and the IPv6 unspecified address (::). This allows unauthenticated attackers to reach internal services and cloud metadata endpoints like 169.254.169.254.

MitigationUpgrade to Crawl4AI version 0.8.8 or later, and enable JWT authentication (jwt_enabled: true) on the Docker API 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.8

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. Check Crawl4AI version
    Identify the installed Crawl4AI version and compare it to the affected range (versions before 0.8.8). Consult your package manager, container image tag, or application startup logs for the version number.
    Affected if The installed version is lower than 0.8.8
  2. Confirm Docker API server is enabled
    Determine whether the Docker API server component is running or configured in your Crawl4AI deployment. This is the component that contains the vulnerable URL validation functions.
    Affected if Docker API server is enabled and accessible to network traffic
  3. Check JWT authentication status
    Inspect the Docker API configuration for the jwt_enabled setting. This setting must be set to true to block unauthenticated exploitation of the SSRF vulnerability.
    Affected if JWT authentication is disabled (jwt_enabled is false or not set)
  4. Identify if URLs can target internal infrastructure
    If the Docker API is exposed, test whether input URLs can reach internal IP addresses in IPv6 transition format (such as ::ffff:10.x.x.x or ::) or cloud metadata endpoints (such as 169.254.169.254).
    Affected if The Docker API accepts URLs that resolve to internal IPv4 addresses encoded as IPv6 transition formats or the IPv6 unspecified address (::)

You are affected if running Crawl4AI version below 0.8.8 with the Docker API server enabled and without JWT authentication configured, as this allows unauthenticated SSRF attacks to internal services.

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

Upgrade to Crawl4AI version 0.8.8 or later, and enable JWT authentication (jwt_enabled: true) on the Docker API to prevent unauthenticated exploitation.

Recommended fix High confidence

0.8.8

  1. Identify the current deployment method (Docker container, pip install, or source)
  2. If using Docker, stop the running Crawl4ai container
  3. Pull the updated Crawl4ai image with tag 0.8.8: docker pull crawl4ai:latest or docker pull crawl4ai:v0.8.8
  4. Remove the old container: docker rm <container_id>
  5. Run the new container with the updated image, ensuring jwt_enabled is set appropriately for your environment
  6. If using pip/package installation, upgrade via: pip install crawl4ai==0.8.8 or pip install --upgrade crawl4ai
  7. Verify the upgrade by checking the version: crawl4ai --version or checking the Docker container logs
  8. Test that the SSRF protection now properly blocks IPv6 transition addresses and the unspecified address (::)

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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