<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T21:25:31.970341+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-57572</id>
    <title>CVE-2026-57572 — Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args</title>
    <updated>2026-10-02T21:25:31.972071+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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'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></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-57572"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-r253-r9jw-qg44</id>
    <title>GHSA-r253-r9jw-qg44 — Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args</title>
    <updated>2026-10-02T21:25:31.972144+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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'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></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-r253-r9jw-qg44"/>
  </entry>
</feed>
