PT-2026-51773 · Crawl4Ai · Crawl4Ai
CVE-2026-56262
·
Published
2026-06-16
·
Updated
2026-07-12
CVSS v4.0
8.8
High
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Name of the Vulnerable Software and Affected Versions
Crawl4AI versions prior to 0.8.7
Description
Multiple security issues affect the Crawl4AI Docker API server across several functional areas:
- An authentication bypass in the monitor router allows unauthenticated access to destructive operations, specifically the
/monitor/actions/cleanupendpoint, enabling remote attackers to manipulate monitoring state and disrupt service. The/monitor/wsWebSocket endpoint is also affected. - Arbitrary file write is possible via the
/screenshotand/pdfendpoints because theoutput pathparameter lacks validation, allowing attackers to overwrite server files or write to any appuser-writable location. - Server-Side Request Forgery (SSRF) occurs via webhook URLs in
/crawl/joband/llm/job, as well as direct crawl endpoints including/crawl,/crawl/stream,/md, and/llm. These allow requests to internal services, Docker networks, and cloud metadata endpoints (169.254.169.254). A bypass for hostname blocklists was identified using IPv6-mapped IPv4 addresses. - Stored Cross-Site Scripting (XSS) exists in the monitor dashboard where crawl URLs and error messages are rendered using
innerHTMLwithout proper escaping, allowing malicious markup to execute in an operator's browser. - Arbitrary JavaScript execution is possible via the
/execute jsendpoint, which runs code in the server's browser with web security disabled, combining JS execution with SSRF capabilities. - A hardcoded JWT secret key defaults to "mysecret", allowing attackers to forge valid authentication tokens.
Recommendations
Update to version 0.8.7 or later.
Set
CRAWL4AI API TOKEN to enable authentication.
Configure a strong SECRET KEY with at least 32 characters when using JWT.
Restrict network access to the Docker API.
As a temporary mitigation, disable the /execute js endpoint by setting the CRAWL4AI EXECUTE JS ENABLED environment variable to false.Exploit
Fix
SSRF
Path traversal
Missing Authentication
Using Hardcoded Credentials
Code Injection
XSS
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Crawl4Ai