Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

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

CVE-2026-28445GHSA-6m7c-xfhp-p9fh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@typebot.io/js 0.10.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-28445: 0.26% estimated exploitation activity in the next 30 days; percentile 17.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The rating block's custom icon feature accepts arbitrary HTML/SVG via the customIcon.svg field and renders it using Solid's innerHTML directive without any sanitization. When a malicious typebot is imported or crafted by a workspace collaborator, the payload executes in the builder's DOM context (builder.typebot.io), bypassing the isUnsafe Web Worker sandbox that protects Script blocks during preview. This allows session hijacking and privilege escalation within the builder application. Severity High (CVSS 3.1: 8.7) CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N - Attack Vector: Network — malicious typebot can be delivered via import/template sharing or crafted by a collaborator - Attack Complexity: Low — payload is a trivial HTML injection, no special conditions required - Privileges Required: Low — attacker needs either collaborator access to a workspace or the ability to distribute a typebot template - User Interaction: Required — victim must preview the bot in the builder -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6m7c-xfhp-p9fh

  2. Revision 1 · created ·

    Published from osv record GHSA-6m7c-xfhp-p9fh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28445

Advisory: Typebot has Stored XSS via Rating Block Custom Icon that Bypasses isUnsafe Sandbox in Builder Preview
IDs: CVE-2026-28445, GHSA-6m7c-xfhp-p9fh
Record: https://patchnext.com/advisories/cve-2026-28445 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @typebot.io/js 0.10.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @typebot.io/js: affected < 0.10.1; fixed in 0.10.1

## Suggested inspection (read-only)
- `npm ls @typebot.io/js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @typebot.io/js.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6m7c-xfhp-p9fh (OSV record GHSA-6m7c-xfhp-p9fh lists affected ranges: npm @typebot.io/js >=0 <0.10.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6m7c-xfhp-p9fh (GitHub-reviewed advisory GHSA-6m7c-xfhp-p9fh lists affected ranges: npm @typebot.io/js >=0 <0.10.1)

Commands are suggestions: review each one before running it.

Loading voting…