← Back
CVE-2026-82286
high
CVSS 8.6
Path Traversal in CVE-2026-82286 (CVE-2026-82286)
Summary
path traversal in CVE-2026-82286 (CVE-2026-82286). Data can be tampered with by attackers. Exploitable via `POST /crawl`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-82286** has been found in CVE-2026-82286.
Attackers can target a specific entry point like `POST /crawl` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-82286 CVE-2026-82286" on the vendor's site.
CVE-2026-82286 (CVE-2026-82286) — CWE-22 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /crawl
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in CVE-2026-82286. Attackers reach the vulnerable code path via `POST /crawl` without authentication.
📍 Affected scope
CVE-2026-82286 — . Attack surface: POST /crawl.
🔥 Severity
Severity: High (CVSS 8.6/10). Data can be tampered with by attackers
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /crawl` requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
3Hunt for indicators of compromise detect
grep 'POST /crawl' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /crawl` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /crawl on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://github.com/BuilderIO/gpt-crawler
- web https://github.com/BuilderIO/gpt-crawler/blob/d2245d66a5ad60bf227a55c849135394cbecc9b5/src/config.ts
- web https://github.com/BuilderIO/gpt-crawler/blob/d2245d66a5ad60bf227a55c849135394cbecc9b5/src/core.ts
- web https://github.com/BuilderIO/gpt-crawler/issues/418
- web https://www.vulncheck.com/advisories/gpt-crawler-arbitrary-file-write-via-outputfilename-parameter
- web https://nvd.nist.gov/vuln/detail/CVE-2026-82286
- web https://github.com/advisories/GHSA-98j5-x6wm-v8hp