What is CVE-2026-28445?

CVE-2026-28445 is a high-severity cross-site scripting (XSS) vulnerability in @typebot.io/js (npm), affecting versions < 0.10.1. It is fixed in 0.10.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-28445?

CVE-2026-28445 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @typebot.io/js are affected by CVE-2026-28445?

@typebot.io/js (npm) versions < 0.10.1 is affected.

Is there a fix for CVE-2026-28445?

Yes. CVE-2026-28445 is fixed in 0.10.1. Upgrade to this version or later.

Is CVE-2026-28445 exploitable, and should I be worried?

Whether CVE-2026-28445 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-28445 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-28445 in @typebot.io/js | Intelligent Application Security

Q: How severe is CVE-2026-28445?

CVE-2026-28445 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @typebot.io/js are affected by CVE-2026-28445?

@typebot.io/js (npm) versions < 0.10.1 is affected.

Q: Is there a fix for CVE-2026-28445?

Yes. CVE-2026-28445 is fixed in 0.10.1. Upgrade to this version or later.

Q: Is CVE-2026-28445 exploitable, and should I be worried?

Whether CVE-2026-28445 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-28445 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-28445?

Upgrade @typebot.io/js to 0.10.1 or later.

Summary

Typebot has Stored XSS via Rating Block Custom Icon that Bypasses isUnsafe Sandbox in Builder Preview

Impact

Session hijacking: Attacker can exfiltrate authentication cookies and session tokens from the builder origin
Privilege escalation: A collaborator with editor access can execute code in the session of workspace admins/owners
Sandbox bypass: Completely circumvents the isUnsafe Web Worker sandbox designed to protect against imported/untrusted bots
Account takeover: With stolen session tokens, the attacker can access the victim's full workspace, modify bots, access integrations, and view collected data
Defense inconsistency: The codebase sanitizes innerHTML in StreamingBubble.tsx but not in RatingForm.tsx, indicating this is an oversight rather than a design choice

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-28445 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.10.1); upgrading removes the vulnerable code path.

Affected versions

@typebot.io/js (< 0.10.1)

Security releases

@typebot.io/js → 0.10.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade @typebot.io/js to 0.10.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-28445? CVE-2026-28445 is a high-severity cross-site scripting (XSS) vulnerability in @typebot.io/js (npm), affecting versions < 0.10.1. It is fixed in 0.10.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2026-28445? CVE-2026-28445 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @typebot.io/js are affected by CVE-2026-28445? @typebot.io/js (npm) versions < 0.10.1 is affected.
Is there a fix for CVE-2026-28445? Yes. CVE-2026-28445 is fixed in 0.10.1. Upgrade to this version or later.
Is CVE-2026-28445 exploitable, and should I be worried? Whether CVE-2026-28445 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-28445 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-28445? Upgrade @typebot.io/js to 0.10.1 or later.

Other vulnerabilities in @typebot.io/js

CVE-2026-39964 CVE-2025-65098