CVE-2026-57573: Crawl4AI is an open-source LLM-friendly web crawler and scraper

Q: How do I fix CVE-2026-57573?

crawl4ai: upgrade to 0.9.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-57573 being exploited?

CVE-2026-57573 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-57573 affect?

CVE-2026-57573 affects crawl4ai. Severity is high (CVSS 8.6). Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed see

Q: How urgent is CVE-2026-57573?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.6REMOTEUPGRADE

CVE-2026-57573 is a high-severity flaw (CVSS 8.6) affecting crawl4ai. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed seed URLs straight to the crawler with no destination validation, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawler_config.stream=true with a URL pointing at an intern

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-07-06
Last modified	2026-10-25

Publisher (CNA): GitHub, Inc. · Vendor: kidocode

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-06 21:16 UTCPublished CVE record published
2026-10-25 20:10 UTCUpdated Record last modified

kidocode crawl4ai UPGRADE

Affected: < 0.9.0

Fixed in: 0.9.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy crawl4ai || rpm -q crawl4ai || crawl4ai --version

2. UPGRADE to 0.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade crawl4ai

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade crawl4ai

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-57573?

crawl4ai: upgrade to 0.9.0. Exact commands for each OS are on this page.

Is CVE-2026-57573 being exploited?

CVE-2026-57573 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-57573 affect?

CVE-2026-57573 affects crawl4ai. Severity is high (CVSS 8.6). Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed see

How urgent is CVE-2026-57573?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

Software pages

Docker vulnerabilities

Related CVEs

CVE-2026-57572 CRITICAL 10.0 UPGRADE Crawl4AI is an open-source LLM-friendly web crawler and scraper
CVE-2026-57571 CRITICAL 9.6 UPGRADE Crawl4AI is an open-source LLM-friendly web crawler and scraper
CVE-2026-56261 HIGH 8.6 UPGRADE Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /

References

← Back to latest CVEs