Live › vulnerability › CVE-2026-119122
Crawl4AI before 0.9.5 has a blind server-side request forgery flaw in its Docker server. An API client can enable check_cache_freshness to bypass the egress proxy and make the server request internal or cloud-metadata addresses, which can reveal internal services.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:25 UTC. All times on this page are UTC.
Teams that run the Crawl4AI Docker server and let API clients reach it can be affected, because the server makes outbound requests on their behalf. Exposure depends on the server being reachable by clients and on the check_cache_freshness path being used; deployments that do not expose the API to untrusted clients can skip it.
No product ranges from the sources yet.
pip show crawl4ai, and compare it to 0.9.5.check_cache_freshness is accepted in requests.0.9.5 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Crawl4AI before 0.9.5 contains a blind server-side request forgery vulnerability in the Docker server that allows API clients to bypass the egress proxy by enabling check_cache_freshness. Attackers can cache a controlled URL, then trigger CacheValidator to follow 302 redirects or DNS rebinding to internal and cloud-metadata addresses for port and service discovery.
This page as .md · .json · in your agent: get_signal("CVE-2026-119122")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.