Live › vulnerability › CVE-2026-112363
Go to dashboardCrawl4AI versions 0.8.7 through 0.9.5 have a server-side request forgery flaw in their Docker API server. An unauthenticated attacker can send crafted URLs with userinfo that bypass destination checks, making the server connect to internal hosts on port 443 and leak certificate details.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running the Crawl4AI Docker API server in versions 0.8.7 through 0.9.5 are exposed, especially if it accepts requests from untrusted clients. The sources say the attack needs fetch_ssl_certificate=true in the request, so deployments that never receive such requests are less exposed. Library-only users who do not run the Docker API server are likely not affected, but the sources do not state this directly.
No product ranges from the sources yet.
pip show crawl4ai or the image tag used in your Docker deployment.0.9.5; the sources do not name the patched release.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Crawl4AI from 0.8.7 through 0.9.5 contains a server-side request forgery vulnerability in the Docker API server that allows unauthenticated attackers to bypass destination checks via URL userinfo parsing differences. Attackers can set fetch_ssl_certificate=true with crafted userinfo URLs so SSLCertificate.from_url connects to internal hosts on port 443, probing reachability and leaking certificate details.
This page as .md · .json · in your agent: get_signal("CVE-2026-112363")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.