dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-33712

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the preview chat endpoint (POST /api/v1/typebots/{typebotId}/preview/startChat) allows unauthenticated users to achieve Server-Side Request Forgery (SSRF) by supplying a custom typebot definition with server-side code blocks. The fetch function exposed inside the isolated-vm sandbox calls Node.js native fetch without the SSRF validation (validateHttpReqUrl) that protects the HTTP Request block. This bypasses all SSRF mitigations added after GHSA-8gq9-rw7v-3jpr. Exploitation of this unauthenticated SSRF vulnerability can lead to cloud credential theft, internal network access and data exfiltration for any self-hosted Typebot deployments and hosted services. This issue has been fixed in version 3.16.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Typebot versions 3.15.2 and prior have an unauthenticated SSRF vulnerability in the preview chat endpoint (POST /api/v1/typebots/{typebotId}/preview/startChat). Attackers can supply custom typebot definitions with server-side code blocks that leverage the fetch function inside an isolated-vm sandbox. This fetch calls Node.js native fetch directly without the validateHttpReqUrl SSRF validation that protects the HTTP Request block, bypassing all SSRF mitigations.

MitigationUpgrade to Typebot version 3.16.0 or later, which contains the fix. For deployments where immediate upgrade is not feasible, disable the preview chat endpoint or implement network-level restrictions to prevent outgoing connections from the Typebot server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your Typebot version
    Locate the running Typebot instance and identify its installed version number (typically visible in package.json, docker image tag, or the application's admin UI footer)
    Affected if The installed version is lower than 3.16.0 (the patched release)
  2. Verify unauthenticated access to the preview endpoint
    Attempt a POST request to /api/v1/typebots/{anyTypebotId}/preview/startChat without providing authentication credentials (no JWT, session cookie, or API key)
    Affected if The endpoint returns a successful response (200 OK) rather than rejecting the request with 401/403
  3. Check if custom typebot definitions are accepted
    Send a POST request to the preview endpoint with a crafted payload containing a typebot definition that includes server-side code blocks (look for 'code' blocks with JavaScript content)
    Affected if The server accepts and processes the custom definition without validation, allowing code block execution
  4. Confirm isolated-vm sandbox is in use
    Inspect the Typebot server's dependencies or configuration to verify the 'isolated-vm' package is installed and active for code execution features
    Affected if isolated-vm is present and the preview endpoint allows code blocks to execute fetch calls

A user is affected if their Typebot installation is below version 3.16.0 AND the /preview/startChat endpoint is accessible without authentication, allowing execution of custom typebot definitions with code blocks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Typebot version 3.16.0 or later, which contains the fix. For deployments where immediate upgrade is not feasible, disable the preview chat endpoint or implement network-level restrictions to prevent outgoing connections from the Typebot server.

Recommended fix High confidence

3.16.0

  1. 1. Identify all self-hosted Typebot deployments running version 3.15.2 or prior
  2. 2. Plan the upgrade to version 3.16.0 during a maintenance window
  3. 3. Backup the current database and configuration files
  4. 4. Stop the Typebot service
  5. 5. Upgrade Typebot to version 3.16.0
  6. 6. Verify the upgrade by checking the version number in the admin interface
  7. 7. Test the /api/v1/typebots/{typebotId}/preview/startChat endpoint to confirm SSRF validation is now applied
  8. 8. Restart the Typebot service

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data