Arbitrary file write via symlinked output paths
Published Jun 23, 2026 · Updated Jun 23, 2026
Path traversal in Crawl4AI before 0.8.8 allows remote attackers to write outside the output directory through unauthenticated API requests. The screenshot and PDF handlers validate output_path without safely resolving symlinked components, then follow the selected path when opening the file. Code execution requires the server runtime account to have write access to an executable, startup, SSH, or cron location.
Summary
What happened
Path traversal in Crawl4AI before 0.8.8 allows remote attackers to write outside the output directory through unauthenticated API requests. The screenshot and PDF handlers validate output_path without safely resolving symlinked components, then follow the selected path when opening the file. Code execution requires the server runtime account to have write access to an executable, startup, SSH, or cron location.
The record
- CVE
- CVE-2026-56258
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Crawl4AI
- Product
- Crawl4AI
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.8.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo