Summary
CVE-2026-82286 is an unauthenticated arbitrary file write vulnerability (CWE-22, Path Traversal) affecting gpt-crawler through version 1.5.1, developed by BuilderIO. The flaw resides in the POST /crawl API endpoint, which fails to validate the outputFileName parameter, allowing remote attackers to write files with attacker-controlled content to arbitrary filesystem locations without authentication. The issue carries a High severity rating (CVSS 8.8).
Technical details
- Root cause: The
POST /crawlendpoint accepts a user-suppliedoutputFileNameparameter and passes it through to file-write logic insrc/core.tsandsrc/config.tswithout canonicalizing or restricting the resulting path. - Trigger conditions: An attacker sends a crawl request specifying an
outputFileNamevalue containing an absolute path or parent-directory traversal sequences (e.g.,../../), combined with a crawl target URL the attacker controls. - Attack vector: Network-based, requires no authentication and no user interaction — the attacker only needs network access to the exposed
/crawlendpoint. - Impact: The server writes the crawled content (sourced from an attacker-controlled URL) to the attacker-specified path, enabling overwrite of existing files on the host filesystem. This can lead to data corruption, configuration tampering, or — depending on what files are overwritten and how the host processes them — a path toward further compromise of the system running gpt-crawler.
Affected software
- BuilderIO gpt-crawler — all versions from 0 through 1.5.1 (inclusive)
Severity
- CVSS v3.1 Base Score: 8.6 (High) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L - CVSS v4.0 Base Score: 8.8 (High) —
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
Mitigation and recommended actions
- Immediate: As of this writing, no patched release of gpt-crawler has been published by the maintainers to address this issue. Organizations should monitor the official BuilderIO gpt-crawler GitHub repository for a fix and upgrade as soon as one becomes available.
- Workarounds / network mitigations (no patch available):
- Do not expose the gpt-crawler
/crawlAPI endpoint directly to untrusted networks or the public internet; restrict access to trusted, authenticated internal callers only. - Place an authentication/authorization layer (e.g., API gateway, reverse proxy with auth) in front of the gpt-crawler service, since the underlying application does not enforce authentication on this endpoint.
- Where feasible, run the gpt-crawler service with a restricted filesystem context (e.g., a container or sandboxed user with write access limited to its intended output directory) to contain the impact of an arbitrary file write.
- Add input validation/allow-listing at a proxy or WAF layer to reject requests where
outputFileNamecontains absolute paths or../traversal sequences. - Monitor for unexpected file creation or modification activity on hosts running gpt-crawler.
- Do not expose the gpt-crawler

