External risk intelligence

TypeBot OAuth Credential Takeover Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-48765

TypeBot is a chatbot builder tool commonly deployed as a web application. These platforms are typically hosted as internet-facing services to allow users to embed and interact with chatbots via public web interfaces, making the application's management console and API endpoints commonly accessible from the internet.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in TypeBot, a chatbot builder tool. This issue allows unauthorized access and potential takeover of OAuth credentials used by workspaces, which could lead to a compromise of integrated services. The main concern is to confirm if your organization uses this technology and is exposed.

Low-privilege users can steal and reassign workspace credentials.
Protects sensitive integrations linked through OAuth credentials.
Confirm TypeBot usage and assess exposure to this risk.

Attack Path

How an attacker could exploit the issue

An attacker with low-level access can steal and reassign an organization's OAuth credentials. This is achieved by first extracting a credential ID from a bot's configuration, then using a crafted request to overwrite it with their own controlled `workspaceId`, ultimately leading to cross-workspace credential takeover.

Requires low-privilege collaborator access.
Overwrite OAuth credentials via an API call.
Allows cross-workspace credential takeover.

Live Threat

Current exploitation, exposure, and threat context

A low-privilege collaborator on TypeBot could potentially extract an OAuth `credentialsId` from a bot configuration. When supported by the advisory, this ID could then be used to overwrite an existing credential, effectively taking over and reassigning it to a different workspace.

OAuth credentials in shared workspaces.
Overwriting credentials via manipulated requests.
Unauthorized access to connected services.

Operational Fix

Recommended remediation, mitigation, and detection steps

System owners and platform teams are likely responsible for addressing this vulnerability in TypeBot. The first practical step is to identify all instances of TypeBot, confirm their external reachability and business criticality, and then assign ownership for remediation planning.

Identify TypeBot instances and assess exposure.
Confirm accountable owner for remediation.
Plan vendor coordination and updates.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is TypeBot?

TypeBot is a chatbot builder tool designed for creating interactive, automated conversation flows. Organizations use it to deploy custom chatbots on websites or within applications to gather information or interact with visitors. It manages these connections through workspaces and various third-party integrations that require OAuth credentials to authenticate and function securely.

What does CVE-2026-48765 mean?

This vulnerability is an Authorization Bypass, specifically classified as CWE-639 (Authorization Bypass Through User-Controlled Key). It means the software fails to properly verify that a user has permission to modify a specific resource. In this case, an attacker can manipulate an API request to overwrite OAuth credentials belonging to a different workspace than the one they are authorized to manage.

How does an attacker trigger this vulnerability?

An attacker needs low-privilege collaborator access to the platform to start. They first extract a target's OAuth ID from a readable bot configuration. They then call the update function while providing a different, attacker-controlled workspace ID. Simply being an unauthenticated visitor does not trigger this; it requires an active, authenticated user account with at least collaborator-level permissions to interact with the workspace settings.

Is my instance of TypeBot relevant to this threat?

According to Halo Surface Signal, TypeBot is typically deployed as an internet-facing web application. If your management console or API endpoints are accessible from the public internet, the risk is higher because the required collaborator access could be gained by unauthorized parties. Internal-only instances still face risks from malicious or compromised internal users.

How do I respond to this vulnerability?

Your first step is to locate all instances of TypeBot within your environment and verify their current version. Since this issue is resolved in version 3.17.0, you should prioritize upgrading any outdated deployments to this version immediately. Once updated, audit your workspace collaborator lists to ensure that only authorized individuals hold active access to your configurations.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.