Path Traversal in TypeBot (CVE-2026-48768)
Summary
Path traversal in TypeBot (CVE-2026-48768). Data can be tampered with by attackers. Exploitable via POST /api/blocks/file-input/v3/generate-upload-url.
Original description
The description as published by the source.
TypeBot is a chatbot builder tool. In versions 3.16.1 and earlier, POST /api/blocks/file-input/v3/generate-upload-url is unauthenticated and uses unsanitized fileName input to construct public/ S3 object keys, while issuing presigned PUT URLs that do not bind Content-Type. As a result, any anonymous visitor to a published bot with a file input can upload attacker-controlled HTML, SVG, or JS to attacker-chosen subpaths, including other tenants’ publicly served result paths, enabling arbitrary content hosting and potential stored XSS on the storage origin. ../ traversal is blocked by S3/MinIO canonicalization (signature mismatch), but forward-slash path injection is exploitable. This issue has been fixed in version 3.17.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48768 has been found in TypeBot.
Attackers can target a specific entry point like POST /api/blocks/file-input/v3/generate-upload-url over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TypeBot CVE-2026-48768" on the vendor's site.
CVE-2026-48768 (TypeBot) — CWE-22 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/blocks/file-input/v3/generate-upload-url
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.
Path traversal (CWE-22) exists in TypeBot. Attackers reach the vulnerable code path via POST /api/blocks/file-input/v3/generate-upload-url without authentication.
Check the vendor advisory for the affected versions of TypeBot. Attack surface: POST /api/blocks/file-input/v3/generate-upload-url.
Severity: Critical (CVSS 9.3/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/blocks/file-input/v3/generate-upload-url requests with malformed payloads or SQL meta-characters. Run grep -r 'TypeBot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'TypeBot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
TypeBotを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/blocks/file-input/v3/generate-upload-url' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/blocks/file-input/v3/generate-upload-urlへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/blocks/file-input/v3/generate-upload-url on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com