CVE-2026-82286

gpt-crawler through version 1.5.1 contains a path traversal flaw (CWE-22) in its POST /crawl endpoint: the outputFileName parameter is not validated, so an unauthenticated attacker can supply an absolute path or parent-directory segments (../) to write files outside the intended output directory. Because the written content is crawled from attacker-controlled URLs, the attacker effectively chooses both the destination file and its contents, allowing overwriting of existing files such as configuration, startup, or cron files, which can escalate the impact to code execution on the host. Anyone running gpt-crawler 1.5.1 or earlier in its API/server mode with the /crawl endpoint reachable by untrusted clients is affected. Exploitation requires no authentication or user interaction, hence the network-vector 8.8 (High) CVSS 4.0 score. There are currently no known public proofs of concept, no CISA KEV listing, and a low EPSS score of 0.3%, indicating limited near-term exploitation risk.

What to do: Upgrade gpt-crawler to a version newer than 1.5.1 as soon as a patched release is available, and until then restrict access to the /crawl endpoint to trusted networks or add authentication in front of it. Ensure outputFileName values are restricted to plain filenames (no absolute paths or ../ segments). Because the flaw allows overwriting arbitrary files, operators should check for unexpected modifications to sensitive paths such as cron jobs, startup scripts, and configuration files.