Vulnerability in TypeBot (CVE-2026-48765)
Summary
Vulnerability in TypeBot (CVE-2026-48765). Confidential information can be exposed externally. Exploitable via credentialsId.
Original description
The description as published by the source.
TypeBot is a chatbot builder tool. Versions prior to 3.17.0 allow a low-privilege read collaborator to extract a workspace OAuth credentialsId from a readable bot configuration and then overwrite that credential through handleUpdateOAuthCredentials() by supplying an attacker-controlled writable workspaceId. The update path validates only the attacker-supplied workspace and then updates the credential record by global id alone, while also rewriting the credential's workspaceId. This allows cross-workspace OAuth credential takeover and reassignment. Version 3.17.0 patches the 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-48765 has been found in TypeBot.
Attackers can target a specific entry point like credentialsId over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TypeBot CVE-2026-48765" on the vendor's site.
CVE-2026-48765 (TypeBot) — CWE-639 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: credentialsId / workspaceId
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-639) exists in TypeBot. Attackers reach the vulnerable code path via credentialsId.
Check the vendor advisory for the affected versions of TypeBot. Attack surface: credentialsId / workspaceId.
Severity: Critical (CVSS 9.9/10). Confidential information can be exposed externally.
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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。