Server-side Request Forgery (SSRF) Affecting crawl4ai package, versions [,0.8.8)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-CRAWL4AI-17661140
- published28 Jun 2026
- disclosed16 Jun 2026
- creditUnknown
Introduced: 16 Jun 2026
NewCVE-2026-53754 (opens in a new tab)How to fix?
Upgrade Crawl4AI to version 0.8.8 or higher.
Overview
Crawl4AI is a 🚀🤖 Crawl4AI: Open-source LLM Friendly Web Crawler & scraper
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the validate_webhook_url and validate_url_destination functions. An attacker can access internal services and cloud metadata endpoints by submitting specially crafted URLs that encode internal IP addresses using IPv6 transition forms or unspecified addresses. This is only exploitable if the API server is left unauthenticated (with jwt_enabled: false).
Workaround
This vulnerability can be mitigated by enabling authentication (CRAWL4AI_API_TOKEN) or restricting the container's outbound network access (such as using an egress firewall or removing metadata routes).