Skip to main content
VulnerabilityPublished

CVE-2026-57573: unclecode crawl4ai · Server-Side Request Forgery (SSRF)

Affects unclecode crawl4aiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 0.9.0 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade crawl4ai and unclecode/crawl4ai to 0.9.0.

Affected software

ProductAffectedFixed in
unclecodecrawl4aiAffected
  • <0.9.0
Fixed in
  • 0.9.0
GitHubunclecode/crawl4aipkg:github/unclecode/crawl4aiOther threatsAffected
  • <0.9.0
Fixed in
  • 0.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in crawl4ai version 0.9.0. Users should upgrade to version 0.9.0 or later to remediate this issue. Since no official remediation level or patch link is provided, verify the upgrade availability from the vendor's official sources. No other mitigations are indicated.

Description

Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed seed URLs straight to the crawler with no destination validation, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawler_config.stream=true with a URL pointing at an internal, private, or link-local address; the server fetched it and streamed the response body back. This issue is fixed in version 0.9.0.

References

Community reviews

Loading reviews…