Unauthenticated file write via unchecked output path
Published Aug 28, 2026 · Updated Aug 28, 2026
Path traversal in Builder.io GPT Crawler 1.5.1 and earlier allows remote attackers to write files via unauthenticated POST /crawl requests. The config schema accepts outputFileName as any string, and writeBatchToFile passes its derived absolute or parent-relative path directly to writeFile. API server mode must be network reachable; successful requests create or overwrite JSON files at any path writable by the server process.
Summary
What happened
Path traversal in Builder.io GPT Crawler 1.5.1 and earlier allows remote attackers to write files via unauthenticated POST /crawl requests. The config schema accepts outputFileName as any string, and writeBatchToFile passes its derived absolute or parent-relative path directly to writeFile. API server mode must be network reachable; successful requests create or overwrite JSON files at any path writable by the server process.
The record
- CVE
- CVE-2026-82286
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Builder.io
- Product
- GPT Crawler
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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 <=1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GitHub issue #418 HTTP proof of conceptproof of concept · demonstrated
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