Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-56260 – Arbitrary File Write Leading to DoS and Potential RCE – Crawl4AI before 0.8.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-56260 is a high-severity path traversal vulnerability (CWE-22) in Crawl4AI’s Docker API server, affecting all versions before 0.8.7. The output_path parameter accepted by the /screenshot and /pdf endpoints performs no filesystem path validation, allowing an unauthenticated remote attacker to write files to any location accessible by the application’s user. The vulnerability carries a CVSS 3.1 score of 9.1 (Critical) and can result in denial of service through overwriting of critical server files, with the potential to escalate to remote code execution depending on the runtime user’s permissions.

Technical details

  • Root cause: The output_path parameter in the Docker API server’s /screenshot and /pdf endpoints accepts absolute paths and path-traversal sequences (e.g., ../) without any validation or restriction, enabling writes outside any intended output directory.
  • Trigger conditions: A crafted HTTP request to either the /screenshot or /pdf endpoint with a malicious output_path value is sufficient to exploit the vulnerability. No authentication, prior access, or user interaction is required.
  • Attack vector: Network-accessible. The Crawl4AI Docker API server listens on port 11235 by default and, in versions prior to 0.8.7, requires no API token by default, making the endpoints fully unauthenticated.
  • Impact: Arbitrary file write to any path writable by the application process. Direct consequences include denial of service through overwriting of critical server or configuration files. Where the runtime user holds broader write permissions, attackers can overwrite cron jobs, SSH authorized keys, startup scripts, or application code to achieve remote code execution.

Affected software

  • Crawl4AI (PyPI: crawl4ai) — all versions before 0.8.7

Severity

CVSS v3.1 base score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Crawl4AI to version 0.8.7 or later, which introduces path validation that restricts output writes to a designated directory.
  • If immediate patching is not feasible: restrict network-level access to the Docker API server (port 11235) to trusted IP ranges only, and set the CRAWL4AI_API_TOKEN environment variable to enforce token-based authentication on all endpoints.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge