CVE-2026-82286

gpt-crawler Arbitrary File Write via outputFileName Parameter

Published Aug 28, 2026 CVSS 4.0 · 8.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in gpt-crawler versions up through 1.5.1. The software fails to validate the outputFileName field in the POST /crawl HTTP request, allowing anyone to write arbitrary files to the file system. An attacker can supply absolute paths or use parent‑directory references, overwriting existing files or creating new ones with content from attacker‑controlled sources. The weakness is an arbitrary file write, mapped to CWE‑22. This capability could enable attackers to replace executable files, modify configuration, or insert malicious scripts, compromising confidentiality, integrity, and availability of the system.

Affected Systems

The affected product is BuilderIO’s gpt‑crawler, a web‑crawler tool. Versions up to and including 1.5.1 are vulnerable. No other versions or additional vendors are listed.

Risk and Exploitability

The CVSS score of 8.8 indicates high severity. The EPSS score is not available, and the vulnerability has not yet been listed in the CISA KEV catalog. The exploit can be performed without authentication by sending an HTTP POST to the /crawl endpoint and providing a crafted outputFileName value. Attackers can choose absolute paths or traverse directories to override critical files. Given the lack of authentication and the ability to write any path, the risk is significant, especially in exposed deployments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest version of gpt-crawler where the outputFileName parameter is properly validated.
  • Restrict access to the /crawl endpoint to authenticated users or within a trusted network segment, or deploy a reverse proxy that enforces authentication.
  • Implement input validation or path sanitization so that outputFileName is limited to a safe directory and disallows absolute paths or directory traversal sequences.

Generated by OpenCVE AI on August 28, 2026 at 22:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Builderio
Builderio gpt-crawler
Vendors & Products Builderio
Builderio gpt-crawler
Type Values Removed Values Added
Description 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.
Title gpt-crawler Arbitrary File Write via outputFileName Parameter
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L'}

cvssV4_0

{'score': 8.8, 'vector': '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'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:20 PM
Reserved
Aug 28, 2026, 11:12 AM
Status
Deferred
Published
Aug 28, 2026, 8:20 PM
Modified
Sep 23, 2026, 5:17 PM