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

New CVE Detected

CVE-2026-56258 – Arbitrary File Write Leading to RCE – Crawl4AI before 0.8.8

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

Summary

CVE-2026-56258 is an arbitrary file write vulnerability in Crawl4AI’s Docker API server, affecting all versions prior to 0.8.8. The flaw exists in the /screenshot and /pdf REST API endpoints, where insufficient validation of the output_path parameter allows unauthenticated remote attackers to write files outside the intended directory via symlink following and Time-of-Check-Time-of-Use (TOCTOU) race conditions. The vulnerability scores 9.2 (Critical) under CVSS 4.0 and can escalate to remote code execution on systems where the runtime user has write access to executable paths or cron locations.

Technical details

  • Root cause: Improper pathname validation (CWE-22) and unsafe symlink resolution (CWE-59) in the output_path parameter handling of the /screenshot and /pdf Docker REST API endpoints
  • Trigger conditions: An attacker sends a crafted unauthenticated HTTP request to either vulnerable endpoint with a manipulated output_path value; full exploitation requires pre-placing a symlink and winning a TOCTOU race condition, making attack complexity High
  • Attack vector: Network-accessible with no authentication required — Crawl4AI’s Docker server exposes a REST API on default port 11235; versions prior to 0.8.8 do not enforce authentication by default
  • Impact: Arbitrary write of attacker-controlled content to any filesystem path accessible to the runtime process; on systems where that user has write access to executable directories or cron locations, this leads to remote code execution and full compromise of confidentiality, integrity, and availability

Affected software

  • Crawl4AI (PyPI): All versions prior to 0.8.8

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Crawl4AI to version 0.8.8 or later, which contains backward-compatible hardening fixes that address the path traversal and symlink vulnerabilities in the screenshot and PDF endpoints
  • Network mitigation: If immediate patching is not feasible, restrict access to the Crawl4AI Docker API port (default 11235) via firewall rules or network segmentation to block unauthenticated external requests

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