GPU VulnDB

Database/AI/ML frameworks & serving

Crawl4AI: CacheValidator freshness check bypasses the egress proxy, giving blind SSRF from the crawler container

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

Impact

Crawl4AI's Docker server is deployed as a crawling backend for LLM and agent pipelines, and its egress proxy is the control that keeps that crawling pointed outward. An API client that enables check_cache_freshness can cache a URL it controls and then have CacheValidator fetch it outside the proxy, following 302 redirects or DNS rebinding to internal and cloud-metadata addresses. The result is blind port and service discovery from inside the cluster - no response body returned to the attacker, so this is reconnaissance against internal endpoints rather than data theft. Where the crawler runs on a fleet node with an instance metadata endpoint reachable, the internal surface it can probe includes that endpoint.

Who can reach it

Any client able to call the Crawl4AI Docker server's API; the scored vector requires no privileges, so an instance reachable without authentication is exposed to anyone who can reach it.

What to do

Upgrade Crawl4AI to 0.9.5 or later and restart the container - a container redeploy, no host maintenance. Until then, disable or reject check_cache_freshness at your own API gateway, and enforce egress restrictions at the network layer rather than inside the application so a bypassed in-process proxy cannot reach RFC1918 or link-local metadata addresses.

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.