<?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-04T16:00:23.439415+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-26217</id>
    <title>CVE-2026-26217 — Crawl4AI &lt; 0.8.0 Docker API Local File Inclusion via file URL Handling</title>
    <updated>2026-10-04T16:00:23.441189+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> unclecode Crawl4AI</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-26217"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vx9w-5cx4-9796</id>
    <title>GHSA-vx9w-5cx4-9796 — Crawl4AI Has Local File Inclusion in Docker API via file:// URLs</title>
    <updated>2026-10-04T16:00:23.441244+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: Crawl4AI</p>
<p>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.</p>
<p>Attack Vector:
```json
POST /execute_js
{
    "url": "file:///etc/passwd",
    "scripts": ["document.body.innerText"]
}
```
Impact</p>
<p>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</p>
<p>Workarounds</p>
<p>1. Disable the Docker API
2. Add authentication to the API
3. Use network-level filtering</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vx9w-5cx4-9796"/>
  </entry>
</feed>
