gpt-crawler Arbitrary File Write via outputFileName Parameter
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.8epss 0.3%
from disclosure to weapon1 days
Published on NVDAug 28
1st PoC+1d
exploitation probability
0.3%top 72% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
Affected products
BuilderIO · gpt-crawlerpublic PoCs found — 1
githubgithub.com/BiiTts/CVE-2026-82286-gpt-crawler-Arbitrary-File-Write★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/BuilderIO/gpt-crawlerhttps://github.com/BuilderIO/gpt-crawler/blob/d2245d66a5ad60bf227a55c849135394cbecc9b5/src/config.tshttps://github.com/BuilderIO/gpt-crawler/blob/d2245d66a5ad60bf227a55c849135394cbecc9b5/src/core.tshttps://github.com/BuilderIO/gpt-crawler/issues/418https://www.vulncheck.com/advisories/gpt-crawler-arbitrary-file-write-via-outputfilename-parameter