Is CVE-2026-57573 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57573 being exploited in the wild.

How severe is CVE-2026-57573?

High severity, with a CVSS score of 8.6, published 6 July 2026.

Which products and versions are affected?

crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.0.

Is there a fix for CVE-2026-57573?

Yes. crawl4ai (PyPI): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-57573 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-57573?

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.

CVE-2026-57573: unclecode Crawl4AI SSRF in Docker API streaming path

CVE-2026-57573 · Severity: high · CVSS 8.6 · Published 2026-07-06

Crawl4AI is an open-source tool used to scrape web content for use with Artificial Intelligence models. A security flaw in its Docker-based server allows unauthorized users to force the tool to access internal company websites or private cloud configuration services that should not be reachable from the public internet. This could lead to the theft of sensitive internal data or cloud access credentials, potentially compromising the entire cloud environment.

Technologies: crawl4ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-57573 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57573 being exploited in the wild.
How severe is CVE-2026-57573?: High severity, with a CVSS score of 8.6, published 6 July 2026.
Which products and versions are affected?: crawl4ai (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.0.
Is there a fix for CVE-2026-57573?: Yes. crawl4ai (PyPI): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57573 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-57573?: 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.9.0 or later
```
pip install "crawl4ai>=0.9.0"
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Crawl4AI's Docker API server due to missing destination validation in the streaming request handler. While the standard `/crawl` path implemented SSRF protections, the `handle_stream_crawl_request` function (used by `/crawl/stream` and `/crawl` with `stream=true`) passed URLs directly to the crawler without checking if they pointed to internal, private, or link-local addresses. An unauthenticated remote attacker can exploit this to scan internal networks or retrieve sensitive data from cloud metadata services (e.g., AWS/GCP metadata endpoints at 169.254.169.254). The issue is resolved in version 0.9.0 by applying global-routability checks to all seed URLs in the streaming handler.

Affected products

unclecode crawl4ai < 0.9.0

Identifiers

CVE-2026-57573
GHSA-wm69-2pc3-rmmf
PYSEC-2026-2140

Timeline

2026-06-18: patched: Fix included in version 0.9.0 release
2026-07-06: disclosed: CVE-2026-57573 published

References

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