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

Back
New CVE Detected

CVE-2026-56261 – SSRF via Unvalidated Webhook URLs – Crawl4AI before 0.8.7

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-56261 is a critical Server-Side Request Forgery (SSRF) vulnerability in the Crawl4AI Docker API server, affecting all versions prior to 0.8.7. The /crawl/job and /llm/job endpoints accept webhook callback URLs as parameters without validating the destination address, enabling unauthenticated remote attackers to force the server to make HTTP requests to internal networks, private IP ranges, Docker-internal hosts, or cloud metadata endpoints. With a CVSS 4.0 score of 9.2 (Critical), this vulnerability poses a severe risk of cloud credential theft and internal network exposure.

Technical details

  • Root cause: The /crawl/job and /llm/job endpoints in Crawl4AI’s Docker API server accept webhook callback URLs as job parameters without performing any destination validation. There is no blocklist, allowlist, or DNS rebinding protection applied to webhook targets.
  • Trigger conditions: An unauthenticated attacker sends a crafted POST request to /crawl/job or /llm/job with a webhook parameter set to an internal IP address, a private RFC 1918 range, a Docker bridge network address, or a cloud instance metadata endpoint such as http://169.254.169.254/latest/meta-data/ (used by AWS IMDSv1, GCP, and Azure).
  • Attack vector: Fully network-accessible with no authentication required. Crawl4AI’s Docker API server runs without authentication by default unless the CRAWL4AI_API_TOKEN environment variable is explicitly configured — the majority of self-hosted instances are unauthenticated.
  • Impact: The server initiates outbound HTTP requests to the attacker-supplied internal destination upon job completion, potentially retrieving cloud provider instance metadata including IAM role credentials (AWS, GCP, Azure), exposing internal microservices, and enabling lateral movement within the container’s host network.

Affected software

  • Crawl4AI Docker API server (unclecode/crawl4ai): all versions prior to 0.8.7

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade Crawl4AI to version 0.8.7 or later, which introduces destination validation for webhook callback URLs in the Docker API server.
  • If immediate patching is not feasible:
    • Restrict network access to the Crawl4AI Docker API (default port 11235) with firewall rules to prevent public internet exposure.
    • Set the CRAWL4AI_API_TOKEN environment variable to enforce token-based authentication on all API endpoints.
    • Apply egress filtering at the container or host network level to block outbound requests from the Crawl4AI container to link-local (169.254.0.0/16) and RFC 1918 private address ranges.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge