CVE-2025-65098: Typebot Credential Theft via Client-Side Script Execution and API Authorization Bypass

@typebot.io/js Updated 22 Jan 2026

Summary

22/01/2026
Yes i
High
7.4

CVE-2025-65098: Typebot affected by Credential Theft via Client-Side Script Execution and API Authorization Bypass. Affects @typebot.io/js versions < 0.9.15. Fixed in 0.9.15. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Typebot is an open-source tool designed for creating interactive bots that can automate tasks and facilitate user interactions. It allows users to build bots using a visual interface, integrating various APIs and services. However, a critical vulnerability has been identified that exposes stored credentials to unauthorized access, compromising user security.

Vulnerability Detail

The vulnerability arises from client-side script execution within Typebot, which enables attackers to steal stored credentials from users. When a user runs a malicious typebot, JavaScript executes in their browser, allowing the attacker to exfiltrate sensitive information such as OpenAI keys, Google Sheets tokens, and SMTP passwords. The API endpoint '/api/trpc/credentials.getCredentials' fails to verify ownership of credentials, allowing any authenticated user to retrieve plaintext API keys by simply altering the credentials ID in the request. This lack of authorization checks poses a significant risk, as attackers can exploit this vulnerability to gain access to sensitive data without user consent.

How To Fix

Latest published version: 0.10.11 as of 23 Oct 2026

npm install @typebot.io/js@0.10.11

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.9.15

This is the first release that contains the fix.

npm install @typebot.io/js@0.9.15

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users should avoid executing typebots from untrusted sources or those that contain script blocks with 'Execute on client' enabled. Additionally, users can manually review and limit the credentials stored in Typebot to minimize exposure.

Conclusion

The CVE-2025-65098 vulnerability in Typebot poses a significant risk to users by allowing unauthorized access to sensitive credentials through client-side script execution. It is crucial for users to update to the patched version and exercise caution when executing typebots from untrusted sources.

See every vulnerability recorded for @typebot.io/js →

Share this vulnerability

FAQ

The vulnerability allows attackers to execute client-side scripts that can steal stored credentials from users when they run a malicious typebot.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors open-source vulnerabilities without requiring installation.

The vulnerability exposes various types of credentials, including OpenAI API keys, Google Sheets tokens, and SMTP passwords.

Yes, a patch is available in version 0.9.15 of the @typebot.io/js package. Users should update to this version to mitigate the vulnerability.

If you suspect that your credentials have been compromised, immediately revoke access to the affected services and update your credentials. Additionally, update your Typebot package to the latest version.

Related vulnerabilities

Recent vulnerabilities recorded for @typebot.io/js.

How To Fix

Latest published version: 0.10.11 as of 23 Oct 2026

npm install @typebot.io/js@0.10.11

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.9.15

This is the first release that contains the fix.

npm install @typebot.io/js@0.9.15

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback