CVE-2026-53754: unclecode Crawl4AI SSRF in Docker API server

CVE-2026-53754 · Severity: high · CVSS 7.5 · Published 2026-06-23

Crawl4AI is an open-source tool used to crawl and scrape websites for use with Large Language Models (LLMs). A security flaw in its Docker API server allows unauthorized users to bypass security filters and force the server to connect to internal network resources or cloud metadata services. This could lead to the exposure of sensitive internal data or cloud service credentials, potentially compromising the entire hosting environment.

Technologies: crawl4ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-53754 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53754 being exploited in the wild.
How severe is CVE-2026-53754?
High severity, with a CVSS score of 7.5, published 23 June 2026.
Which products and versions are affected?
crawl4ai (PyPI) <= 0.8.7, ECOSYSTEM:introduced=0,fixed=0.8.8.
Is there a fix for CVE-2026-53754?
Yes. crawl4ai (PyPI): upgrade to 0.8.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53754 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-53754?
Check whether you run crawl4ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • crawl4ai (PyPI): upgrade to 0.8.8 or later
    pip install "crawl4ai>=0.8.8"

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Crawl4AI's Docker API server due to insufficient validation in the 'validate_webhook_url' and 'validate_url_destination' functions. The protection mechanism relied on an explicit CIDR blocklist that failed to account for various IPv6 transition forms (such as NAT64, 6to4, and IPv4-mapped addresses) and the IPv6 unspecified address. An unauthenticated remote attacker can exploit this by submitting specially crafted URLs to API endpoints (e.g., /crawl, /md, /crawl/job), causing the server to bypass filters and access internal-only services or cloud metadata endpoints (like 169.254.169.254). The issue is fixed in version 0.8.8 by implementing a more robust check that rejects any non-global IP addresses.

Affected products

  • unclecode crawl4ai < 0.8.8

Identifiers

  • CVE-2026-53754
  • GHSA-4qqr-vv2q-cmr5
  • PYSEC-2026-587

Timeline

  • 2026-06-04: advisory: GitHub advisory published by maintainers
  • 2026-06-23: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.