Live › vulnerability › CVE-2026-119121
Crawl4AI versions from 0.9.0 before 0.9.5 let an authenticated client of the Docker API server inject JavaScript through the css_selector and wait_for fields. The injected script runs in the crawled page, so an attacker can alter page state and the content the crawl returns.
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 API server with 0.9.0 up to but not including 0.9.5. Exposure requires an authenticated API client who can send css_selector or wait_for values; teams using Crawl4AI only as a library or not exposing the API server can likely skip it.
No product ranges from the sources yet.
pip show crawl4ai or the image tag of the Docker deployment.0.9.5 or later, per the advisory's fixed range (from 0.9.0 before 0.9.5 is affected).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Crawl4AI from 0.9.0 before 0.9.5 contains a JavaScript injection vulnerability in the Docker API server that allows authenticated API clients to run arbitrary JavaScript in the crawl page via allowlisted css_selector and wait_for fields. Attackers can inject quotes into css_selector or supply js: conditions in wait_for, bypassing the js_code block to alter page state and returned crawl content.
This page as .md · .json · in your agent: get_signal("CVE-2026-119121")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.