Path Traversal in crawl4ai (CVE-2026-56260)
Summary
Path traversal in crawl4ai (CVE-2026-56260). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.8.7 or later.
Original description
The description as published by the source.
Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-56260 has been found in crawl4ai.
Risk of unauthorized operations or information disclosure. CVSS score: 9.1/10.
What to do: upgrade crawl4ai to 0.8.7 or later.
If unsure, ask your IT team or search "crawl4ai CVE-2026-56260" on the vendor's site.
CVE-2026-56260 (crawl4ai) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.8.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in crawl4ai.
Check the vendor advisory for the affected versions of crawl4ai.
Severity: Critical (CVSS 9.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.8.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'crawl4ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'crawl4ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
crawl4aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade crawl4ai to 0.8.7ステージング環境で 0.8.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory vulncheck.com
- advisory vulncheck.com
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- package github.com