CVE-2026-57573: CWE-918: Server-Side Request Forgery (SSRF) in unclecode crawl4ai
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.
AI Analysis
Technical Summary
The SSRF vulnerability in crawl4ai before version 0.9.0 occurs because the streaming crawl request handler (handle_stream_crawl_request) does not validate destination URLs, unlike the non-streaming /crawl path. This allows remote unauthenticated clients to cause the server to make HTTP requests to internal, private, or link-local addresses by submitting crafted URLs in streaming crawl requests. The server then fetches and streams the response body back to the client, potentially exposing internal resources. The vulnerability is resolved in crawl4ai version 0.9.0.
Potential Impact
An unauthenticated remote attacker can exploit this SSRF vulnerability to make the vulnerable server perform HTTP requests to internal or private network addresses. This can lead to unauthorized access to internal services or information disclosure. The CVSS 3.1 base score is 8.6 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, scope change, and high confidentiality impact with no integrity or availability impact.
Mitigation Recommendations
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.
CVE-2026-57573: CWE-918: Server-Side Request Forgery (SSRF) in unclecode crawl4ai
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.
CVSS v3.1
Score 8.6high
Affected software
pkg:github/unclecode/crawl4aiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The SSRF vulnerability in crawl4ai before version 0.9.0 occurs because the streaming crawl request handler (handle_stream_crawl_request) does not validate destination URLs, unlike the non-streaming /crawl path. This allows remote unauthenticated clients to cause the server to make HTTP requests to internal, private, or link-local addresses by submitting crafted URLs in streaming crawl requests. The server then fetches and streams the response body back to the client, potentially exposing internal resources. The vulnerability is resolved in crawl4ai version 0.9.0.
Potential Impact
An unauthenticated remote attacker can exploit this SSRF vulnerability to make the vulnerable server perform HTTP requests to internal or private network addresses. This can lead to unauthorized access to internal services or information disclosure. The CVSS 3.1 base score is 8.6 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, scope change, and high confidentiality impact with no integrity or availability impact.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-24T18:49:56.207Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4c11fc27e9c797192ee551
Added to database: 07/06/2026, 20:37:16 UTC
Last enriched: 07/14/2026, 09:00:42 UTC
Last updated: 08/20/2026, 22:52:13 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.