Description
gpt-crawler through 1.5.1 fails to validate the outputFileName parameter in the POST /crawl endpoint, allowing unauthenticated attackers to write arbitrary files to any filesystem path. Attackers can supply absolute paths or parent-directory segments to overwrite existing files with content sourced from attacker-controlled URLs.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| BuilderIO | gpt-crawler | ≤ 1.5.1 | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
BiiTts/CVE-2026-82286-gpt-crawler-Arbitrary-File-Write ★ 0 · Aug 29, 2026
CVE-2026-82286 — gpt-crawler <=1.5.1 unauthenticated arbitrary file write via outputFileName (POST /crawl). PoC + self-contained Docker lab. CVSS 8.6, CWE-22.
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
References
- GitHub Issue #418 issue-tracking
- https://github.com/BuilderIO/gpt-crawler product
- Vulnerable code: core.ts technical-description
- Vulnerable code: config.ts technical-description
- VulnCheck Advisory: gpt-crawler Arbitrary File Write via outputFileName Parameter third-party-advisory