GPU VulnDB

Database/AI/ML frameworks & serving

Crawl4AI: robots.txt fetch bypasses egress controls, giving blind SSRF to metadata endpoints

CVSS 6.9CVE-2026-109239AI/ML frameworks & servingcurated

Impact

The robots.txt fetch in RobotsParser.can_fetch does not apply the egress restrictions the rest of the Crawl4AI Docker server enforces. An unauthenticated caller who can set check_robots_txt can use redirects or DNS rebinding to make the crawler issue requests to loopback, internal RFC1918 and cloud metadata addresses. Crawl4AI is commonly run as a shared scraping or ingestion service next to model-serving and data pipelines, so the request originates from inside the cluster network with whatever node identity that pod carries - the classic path to an instance metadata credential or to internal admin APIs. The advisory scores it as blind SSRF for service discovery and low confidentiality impact; it does not establish credential retrieval.

Who can reach it

Anyone who can submit a crawl request to the Crawl4AI Docker server, unauthenticated. Exposure depends on whether that server is reachable from tenant networks or only from trusted pipeline code.

What to do

Upgrade Crawl4AI to 0.9.4 or later and restart the container - a service restart, no node maintenance. Additionally enforce egress at the network layer rather than in the application: block the metadata IP (169.254.169.254), require IMDSv2-style hop limits, and deny the crawler pod access to internal management subnets.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.