gpt-crawler Arbitrary File Write via outputFileName Parameter
Published Aug 28, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
gpt-crawler Arbitrary File Write via outputFileName Parameter
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GitHub advisory ↗
- Source repository ↗
- Source repository ↗
- Source repository ↗
- VulnCheck Advisory: gpt-crawler Arbitrary File Write via outputFileName Parameter ↗
Record history
Published Aug 28, 2026 · Last refreshed Nov 3, 2026