PYSEC-2026-34

Vulnerability from pysec - Published: 2026-02-12 16:16 - Updated: 2026-05-20 09:18
VLAI
Details

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.

Impacted products
Name purl
crawl4ai pkg:pypi/crawl4ai

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "crawl4ai",
        "purl": "pkg:pypi/crawl4ai"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.8.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.3.0",
        "0.3.1",
        "0.3.2",
        "0.3.3",
        "0.3.4",
        "0.3.5",
        "0.3.6",
        "0.3.7",
        "0.3.71",
        "0.3.72",
        "0.3.73",
        "0.3.731",
        "0.3.74",
        "0.3.741",
        "0.3.742",
        "0.3.743",
        "0.3.744",
        "0.3.745",
        "0.3.746",
        "0.3.8",
        "0.4.0",
        "0.4.1",
        "0.4.21",
        "0.4.22",
        "0.4.23",
        "0.4.24",
        "0.4.241",
        "0.4.242",
        "0.4.243",
        "0.4.244",
        "0.4.245",
        "0.4.246",
        "0.4.247",
        "0.4.248",
        "0.4.248b3",
        "0.4.3b1",
        "0.4.3b2",
        "0.4.3b3",
        "0.5.0",
        "0.5.0.post1",
        "0.5.0.post2",
        "0.5.0.post3",
        "0.5.0.post4",
        "0.5.0.post5",
        "0.5.0.post6",
        "0.5.0.post7",
        "0.5.0.post8",
        "0.6.0",
        "0.6.0rc1",
        "0.6.1",
        "0.6.2",
        "0.6.3",
        "0.7.0",
        "0.7.1",
        "0.7.2",
        "0.7.3",
        "0.7.4",
        "0.7.5",
        "0.7.6",
        "0.7.7",
        "0.7.8"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-26217",
    "GHSA-vx9w-5cx4-9796"
  ],
  "details": "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.",
  "id": "PYSEC-2026-34",
  "modified": "2026-05-20T09:18:55.806419Z",
  "published": "2026-02-12T16:16:17.620Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/unclecode/crawl4ai/blob/main/docs/blog/release-v0.8.0.md"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/unclecode/crawl4ai/security/advisories/GHSA-vx9w-5cx4-9796"
    },
    {
      "type": "ADVISORY",
      "url": "https://www.vulncheck.com/advisories/crawl4ai-docker-api-local-file-inclusion-via-file-url-handling"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…