<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 16:00:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-26217 — Crawl4AI &lt; 0.8.0 Docker API Local File Inclusion via file URL Handling</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-26217</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unclecode Crawl4AI&lt;/p&gt;
&lt;p&gt;Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unclecode Crawl4AI&lt;/p&gt;
&lt;p&gt;Crawl4AI versions prior to 0.8.0 contain a local file inclusion vulnerability in the Docker API deployment. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing unauthenticated remote attackers to read arbitrary files from the server filesystem. An attacker can access sensitive files such as /etc/passwd, /etc/shadow, application configuration files, and environment variables via /proc/self/environ, potentially exposing credentials, API keys, and internal application structure.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-26217</guid>
    </item>
    <item>
      <title>GHSA-vx9w-5cx4-9796 — Crawl4AI Has Local File Inclusion in Docker API via file:// URLs</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vx9w-5cx4-9796</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Crawl4AI&lt;/p&gt;
&lt;p&gt;A local file inclusion vulnerability exists in the Crawl4AI Docker API. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing attackers to read arbitrary files from the server filesystem.&lt;/p&gt;
&lt;p&gt;Attack Vector:
```json
POST /execute_js
{
    &amp;#34;url&amp;#34;: &amp;#34;file:///etc/passwd&amp;#34;,
    &amp;#34;scripts&amp;#34;: [&amp;#34;document.body.innerText&amp;#34;]
}
```
Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can:
- Read sensitive files (/etc/passwd, /etc/shadow, application configs)
- Access environment variables via /proc/self/environ
- Discover internal application structure
- Potentially read credentials and API keys&lt;/p&gt;
&lt;p&gt;Workarounds&lt;/p&gt;
&lt;p&gt;1. Disable the Docker API
2. Add authentication to the API
3. Use network-level filtering&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Crawl4AI&lt;/p&gt;
&lt;p&gt;A local file inclusion vulnerability exists in the Crawl4AI Docker API. The /execute_js, /screenshot, /pdf, and /html endpoints accept file:// URLs, allowing attackers to read arbitrary files from the server filesystem.&lt;/p&gt;
&lt;p&gt;Attack Vector:
```json
POST /execute_js
{
    &amp;#34;url&amp;#34;: &amp;#34;file:///etc/passwd&amp;#34;,
    &amp;#34;scripts&amp;#34;: [&amp;#34;document.body.innerText&amp;#34;]
}
```
Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can:
- Read sensitive files (/etc/passwd, /etc/shadow, application configs)
- Access environment variables via /proc/self/environ
- Discover internal application structure
- Potentially read credentials and API keys&lt;/p&gt;
&lt;p&gt;Workarounds&lt;/p&gt;
&lt;p&gt;1. Disable the Docker API
2. Add authentication to the API
3. Use network-level filtering&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vx9w-5cx4-9796</guid>
    </item>
  </channel>
</rss>
