CVE-2026-56260: Crawl4AI SSRF Vulnerability in Webhook URL Handling
Summary
CVE-2026-56260: 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. Affects crawl4ai versions < 0.8.7. Fixed in 0.8.7. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Crawl4AI is an open-source tool designed for web crawling and AI integration, allowing users to automate data collection and processing tasks. The package is widely used for its ability to interface with various AI models and APIs. However, prior to version 0.8.7, it contained a significant security flaw that exposed it to server-side request forgery (SSRF) attacks, compromising the integrity of internal services.
Vulnerability Detail
Crawl4AI before version 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints. These endpoints accept webhook URLs without proper validation, allowing attackers to supply malicious URLs that point to private or internal IP ranges, Docker networks, or cloud metadata endpoints (e.g., 169.254.169.254). This could lead to unauthorized access to sensitive internal services and the potential exposure of cloud metadata, which can be exploited for further attacks.
How To Fix
Latest published version: 0.9.5 as of 23 Oct 2026
pip install --upgrade "crawl4ai==0.9.5"
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.8.7
This is the first release that contains the fix.
pip install --upgrade "crawl4ai==0.8.7"
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can restrict access to the affected endpoints or implement additional validation on the webhook URLs to ensure they do not point to internal resources. This can be done by modifying the server configuration or adding middleware to filter incoming requests.
Conclusion
The SSRF vulnerability in Crawl4AI prior to version 0.8.7 poses a significant risk by allowing attackers to exploit unvalidated webhook URLs. It is crucial to update to the latest version to safeguard against potential attacks and protect sensitive internal services.
See every vulnerability recorded for crawl4ai →
FAQ
Server-side request forgery (SSRF) is a type of attack where an attacker can make requests from the server to internal or external resources, potentially exposing sensitive data.
You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring any signup.
If exploited, this vulnerability could allow attackers to access internal services, leading to data breaches or unauthorized actions within your network.
Yes, you can implement additional validation on the webhook URLs to ensure they do not point to internal resources or restrict access to the affected endpoints.
The CVSS score of this vulnerability is 7.5, indicating a high severity level.
Related vulnerabilities
Recent vulnerabilities recorded for crawl4ai.