Vulnerability in TypeBot (CVE-2026-48763)
Summary
Vulnerability in TypeBot (CVE-2026-48763). Data can be tampered with by attackers. Exploitable via GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url.
Original description
The description as published by the source.
TypeBot is a chatbot builder tool. Versions prior to 3.17.0 expose a deprecated public upload endpoint at GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url that accepts an attacker-controlled filePath and returns a presigned S3 PUT URL for that exact key. Because the endpoint only checks that the referenced typebot is public and that the referenced block is a file input block, an unauthenticated attacker who knows a valid public typebotId and blockId can request presigned upload URLs for arbitrary objects in the shared bucket, including private/... and other tenants' public/... paths. Version 3.17.0 fixes this issue.
Source: NIST National Vulnerability Database NVD
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-48763 has been found in TypeBot.
Attackers can target a specific entry point like GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TypeBot CVE-2026-48763" on the vendor's site.
CVE-2026-48763 (TypeBot) — CWE-862 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url / filePath / PUT / typebotId
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.
A vulnerability (CWE-862) exists in TypeBot. Attackers reach the vulnerable code path via GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url without authentication.
Check the vendor advisory for the affected versions of TypeBot. Attack surface: GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url / filePath / PUT / typebotId.
Severity: High (CVSS 8.2/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 GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/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 'GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-urlへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。