dbcve.org
Crawl4aiApplication · Kidocode

CVE-2026-56259

HIGH · 8.2 CVSS v3.1 Published 2026-07-12
Fix available
A fix is available. Upgrade to 0.8.8 or later.
See remediation →
91/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.8 contains credential exfiltration vulnerabilities in the Docker API server that allow attackers to redirect LLM API calls to attacker-controlled endpoints and read arbitrary environment variables. Attackers can exploit the unauthenticated /md, /llm, and /llm/job endpoints by supplying a malicious base_url parameter and setting api_token to env:VARIABLE_NAME to exfiltrate provider API keys and server secrets including JWT SECRET_KEY for authentication bypass.

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 0.8.8 has unauthenticated Docker API server endpoints (/md, /llm, /llm/job) that accept a malicious base_url parameter and api_token=env:VARIABLE_NAME syntax, allowing attackers to redirect LLM API calls to attacker-controlled endpoints and exfiltrate any environment variable including provider API keys and JWT SECRET_KEY for authentication bypass.

MitigationUpgrade to Crawl4AI 0.8.8 or later. If immediate upgrade is not possible, disable or restrict access to the Docker API server endpoints and rotate any potentially exposed credentials.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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
    Run 'pip show crawl4ai' or check the installed package version via your dependency manager. If running from source, check the version file or git tag.
    Affected if The installed version is earlier than 0.8.8
  2. Determine if Docker API server is enabled
    Inspect your Crawl4AI configuration files and running processes. Look for settings related to the Docker API server component. Check for any startup flags or environment variables that enable this feature.
    Affected if The Docker API server feature is enabled in your deployment
  3. Verify endpoint exposure
    Check if the /md, /llm, or /llm/job endpoints are publicly accessible or accessible without authentication. Inspect your network configuration, firewall rules, and reverse proxy settings.
    Affected if These endpoints are reachable without authentication from untrusted networks
  4. Inspect API token configuration
    Review your application configuration for any api_token parameters that use the 'env:VARIABLE_NAME' syntax. Check if environment variables containing sensitive credentials could be referenced in this manner.
    Affected if Your configuration allows api_token=env:VARIABLE_NAME syntax to reference sensitive environment variables

You are affected if running Crawl4AI version below 0.8.8 with the Docker API server enabled and its /md, /llm, or /llm/job endpoints accessible without authentication.

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 0.8.8 or later. If immediate upgrade is not possible, disable or restrict access to the Docker API server endpoints and rotate any potentially exposed credentials.

Recommended fix High confidence

0.8.8

  1. Upgrade Crawl4ai to version 0.8.8 or later by updating your Docker image or package installation
  2. Verify the upgrade was successful by checking the installed version
  3. Rotate any credentials that may have been exposed, as the vulnerability allowed exfiltration of environment variables including API keys and JWT secrets

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

Fix this in Crawl4ai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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