CVE-2026-56261 - Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /

CVE-2026-56261 + Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server’s / + Critical + 2026-07-10

One-sentence business risk

Server-side request forgery can bridge from the public app into cloud metadata and private network services.

Research notes

  • Root cause: 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.
  • Affected versions: Crawl4AI Crawl4AI: 0 to < 0.8.7.
  • Fixed / safe versions: 0.8.7.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 9.2 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N.

Exact vulnerable code pattern

http_client.get(user_supplied_url_or_import)

Fixed / mitigated code pattern

disable external imports and allow only approved schemes, hosts, and network ranges

Dependency or runtime update:

go list -m all | grep -i affected component || true
go get affected component@latest
go mod tidy
go test ./...

Step-by-step integration guide

  1. Inventory affected component across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to 0.8.7 or apply the exact vendor patch referenced below.
  3. Replace the vulnerable ssrf pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-56261-crawl4ai-before-0-8-7-contains-a-server-side-req
source: "MITRE CVE List V5"
dependency_or_product: "affected component"
affected: "Crawl4AI Crawl4AI: 0 to < 0.8.7"
fixed: "0.8.7"
signals:
  - "ssrf"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-56261 (Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to 0.8.7. Replace the vulnerable ssrf pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-56261, ssrf, affected component, MITRE CVE List V5.
  • Affected tech stack: go.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, zero_day_gold.

References