https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 21:25:24 +0000 https://cve.radiocsirt.org/vuln/cve-2026-57572 <p><strong>Affected:</strong> unclecode crawl4ai</p> <p>Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium&#39;s launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container&#39;s runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.</p> <p><strong>Affected:</strong> unclecode crawl4ai</p> <p>Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium&#39;s launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container&#39;s runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.</p> https://cve.radiocsirt.org/vuln/cve-2026-57572 https://cve.radiocsirt.org/vuln/ghsa-r253-r9jw-qg44 <p><strong>Affected:</strong> PyPI: crawl4ai</p> <p>### Summary</p> <p>The Docker API server accepted a request-supplied `browser_config.extra_args`, which flowed into Chromium&#39;s launch arguments. An attacker could inject Chromium switches that replace a child-process launch command (`--utility-cmd-prefix`, `--renderer-cmd-prefix`, `--gpu-launcher`, `--browser-subprocess-path`) together with `--no-zygote`, causing Chromium to fork/exec an attacker-controlled command as the container&#39;s runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution.</p> <p>The earlier `extra_args` SSRF patch (0.8.9) used a denylist scoped to proxy/DNS flags; a denylist of launch switches is inherently incomplete, and these command-execution switches were not covered.</p> <p>### Affected paths</p> <p>`/crawl`, `/crawl/stream`, `/crawl/job` accepting a request `browser_config.extra_args`.</p> <p>### Impact</p> <p>Unauthenticated remote code execution as the container runtime user; full read/write of application data, mounted secrets, environment, and tokens, and out-of-band exfiltration independent of the HTTP response.</p> <p>### Fix</p> <p>0.9.0 establishes a trust boundary for request-supplied configuration: `extra_args` (along with other power fields such as `proxy`, `user_data_dir`, `cdp_url`, `init_scripts`) is a forbidden field for untrusted request bodies. Any request that sets `extra_args` is rejected with HTTP 400 rather than scrubbed against an always-incomplete denylist. In-process SDK callers (trusted) are unaffected.</p> <p>### Workar…</p> <p><strong>Affected:</strong> PyPI: crawl4ai</p> <p>### Summary</p> <p>The Docker API server accepted a request-supplied `browser_config.extra_args`, which flowed into Chromium&#39;s launch arguments. An attacker could inject Chromium switches that replace a child-process launch command (`--utility-cmd-prefix`, `--renderer-cmd-prefix`, `--gpu-launcher`, `--browser-subprocess-path`) together with `--no-zygote`, causing Chromium to fork/exec an attacker-controlled command as the container&#39;s runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution.</p> <p>The earlier `extra_args` SSRF patch (0.8.9) used a denylist scoped to proxy/DNS flags; a denylist of launch switches is inherently incomplete, and these command-execution switches were not covered.</p> <p>### Affected paths</p> <p>`/crawl`, `/crawl/stream`, `/crawl/job` accepting a request `browser_config.extra_args`.</p> <p>### Impact</p> <p>Unauthenticated remote code execution as the container runtime user; full read/write of application data, mounted secrets, environment, and tokens, and out-of-band exfiltration independent of the HTTP response.</p> <p>### Fix</p> <p>0.9.0 establishes a trust boundary for request-supplied configuration: `extra_args` (along with other power fields such as `proxy`, `user_data_dir`, `cdp_url`, `init_scripts`) is a forbidden field for untrusted request bodies. Any request that sets `extra_args` is rejected with HTTP 400 rather than scrubbed against an always-incomplete denylist. In-process SDK callers (trusted) are unaffected.</p> <p>### Workar…</p> https://cve.radiocsirt.org/vuln/ghsa-r253-r9jw-qg44