PT-2026-54027

CVE-2026-56264

Published

2026-06-16

Updated

2026-07-12

Description by

CVSS 4.0

9.2

Critical

MetricsAV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

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:

The /execute js endpoint allows arbitrary JavaScript execution in the server's browser context because --disable-web-security is enabled, which can be used to perform server-side request forgery (SSRF) against internal services.
The /screenshot and /pdf endpoints are susceptible to arbitrary file write via the output path parameter, allowing attackers to overwrite server files or write to any appuser-writable location.
SSRF is possible through the /crawl/job and /llm/job endpoints via webhook URLs, as well as through the /crawl, /crawl/stream, /md, and /llm endpoints. Attackers can bypass internal-address blocklists using IPv6-mapped IPv4 addresses to access internal services and cloud metadata endpoints.
An authentication bypass exists in the monitor router, making endpoints such as /monitor/actions/cleanup accessible without authentication.
The monitor dashboard is vulnerable to stored cross-site scripting (XSS) because it renders crawl URLs and error messages using innerHTML without proper escaping.
The system uses a hardcoded JWT secret key defaulting to mysecret, enabling the forgery of 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 for 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.

Exploitability

Exploit

Fix

Impacts