Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.6amended

Crawl4AI: Arbitrary file write (path traversal) in crawler downloads can lead to RCE

CVE-2026-57571GHSA-2jq4-q6vv-4cp3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (crawl4ai 0.9.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI crawl4ai

    Affected
    <= 0.8.9
    Fixed in
    0.9.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-57571: 0.81% estimated exploitation activity in the next 30 days; percentile 56.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When the crawler saves a downloaded file, the destination filename was taken from attacker-influenced input and joined to the downloads directory with no confinement. A filename containing an absolute path (e.g. /etc/cron.d/evil) or ../ traversal escaped the downloads directory, giving an arbitrary file write with attacker-controlled contents. Because the written bytes are attacker-controlled, this escalates to remote code execution (overwriting a shell rc-file, ~/.ssh/authorizedkeys, a cron entry, or a Python module on the import path). Affected paths Two download sinks in crawl4ai/asynccrawlerstrategy.py: - HTTP crawler (AsyncHTTPCrawlerStrategy): the filename is parsed from the response Content-Disposition header by extractfilename() and written via aiofiles.open(filepath, 'wb'). Reachable directly via the SDK, and via the unauthenticated Docker /crawl endpoint when an HTTPCrawlerConfig is supplied. - Browser crawler (AsyncPlaywrightCrawlerStrategy): the download's…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-2jq4-q6vv-4cp3

  2. Revision 2 · amended ·

    Amended from osv record GHSA-2jq4-q6vv-4cp3

  3. Revision 1 · created ·

    Published from ghsa record GHSA-2jq4-q6vv-4cp3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57571

Advisory: Crawl4AI: Arbitrary file write (path traversal) in crawler downloads can lead to RCE
IDs: CVE-2026-57571, GHSA-2jq4-q6vv-4cp3
Record: https://patchnext.com/advisories/ghsa-2jq4-q6vv-4cp3 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: crawl4ai 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI crawl4ai: affected <= 0.8.9; fixed in 0.9.0

## Suggested inspection (read-only)
- `python -m pip show crawl4ai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on crawl4ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2jq4-q6vv-4cp3 (GitHub-reviewed advisory GHSA-2jq4-q6vv-4cp3 lists affected ranges: PyPI crawl4ai >=0 <=0.8.9)
- Verified: https://osv.dev/vulnerability/GHSA-2jq4-q6vv-4cp3 (OSV record GHSA-2jq4-q6vv-4cp3 lists affected ranges: PyPI crawl4ai >=0 <0.9.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…