Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82286 – Unauthenticated Arbitrary File Write – gpt-crawler ≤1.5.1

Be the first to know when new zero-days emerge:

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 /crawl endpoint accepts a user-supplied outputFileName parameter and passes it through to file-write logic in src/core.ts and src/config.ts without canonicalizing or restricting the resulting path.
  • Trigger conditions: An attacker sends a crawl request specifying an outputFileName value 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 /crawl endpoint.
  • 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 /crawl API 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 outputFileName contains absolute paths or ../ traversal sequences.
    • Monitor for unexpected file creation or modification activity on hosts running gpt-crawler.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge