dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-49213

HIGH · 8.1 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click Patch available 6 weeks old

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. Prior to 3.17.2, Typebot's shared SSRF validator in packages/lib/src/ssrf/validateHttpReqUrl.ts can be bypassed with the IPv6 unspecified address :: because validateIPAddress blocks local, metadata, and private ranges but does not block :: or its expanded form. A workspace editor or creator can configure a server-side HTTP Request block or guarded script fetch to make the Typebot server connect to local HTTP services through safeKy, including flows triggered by POST /v1/typebots/{publicId}/startChat or POST /v1/sessions/{sessionId}/continueChat. This issue is fixed in version 3.17.2.

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's SSRF validator fails to block the IPv6 unspecified address (::) when validating HTTP request URLs. The validateIPAddress function blocks local, metadata, and private IP ranges but omits :: or its expanded form, allowing workspace editors or creators to make the server connect to local HTTP services through the server-side HTTP Request block.

MitigationUpgrade to TypeBot version 3.17.2 or later which includes the fix to block the IPv6 unspecified address in the SSRF validator.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify TypeBot version
    Check your TypeBot installation's package.json or running application version. Common locations: check package.json in the deployment directory, or query the application's /api/health or version endpoint if available.
    Affected if Version is earlier than 3.17.2 (the fix version that blocks IPv6 unspecified address ::)
  2. Locate the SSRF validator file
    Navigate to packages/lib/src/ssrf/validateHttpReqUrl.ts in your TypeBot source code deployment. Inspect the validateHttpReqUrl function for IPv6 address handling logic.
    Affected if The file exists and the validation logic does not include a check for the IPv6 unspecified address (::) or its expanded form (0000:0000:0000:0000:0000:0000:0000:0000)
  3. Check validateIPAddress function scope
    In the same codebase, locate the validateIPAddress function (likely in packages/lib/src/ssrf/). Review whether it only handles IPv4 ranges (local, metadata, private) or also covers IPv6 loopback/unspecified addresses.
    Affected if The function blocks IPv4 private/local ranges but does not block IPv6 unspecified address :: or IPv6 loopback ::1
  4. Determine if HTTP Request block is in use
    Review your TypeBot flows for any configured HTTP Request blocks or guarded script fetch actions. Check flow configuration files or database records of flow definitions.
    Affected if HTTP Request block or guarded script fetch is enabled and accessible to authenticated workspace editors or creators
  5. Verify internal service exposure
    Assess whether internal HTTP services (localhost, 127.0.0.1, metadata endpoints, internal networks) are accessible from the TypeBot server. Test if the HTTP Request block can reach these endpoints.
    Affected if Internal services are reachable via HTTP Request block from the TypeBot environment

Your environment is affected if running TypeBot versions prior to 3.17.2 AND the HTTP Request block or guarded script fetch feature is accessible to authenticated users, allowing potential connection to internal services via the unblocked IPv6 :: address.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to TypeBot version 3.17.2 or later which includes the fix to block the IPv6 unspecified address in the SSRF validator.

Recommended fix High confidence

3.17.2

  1. Identify the current TypeBot installation version using your package manager or deployment method
  2. If using npm/npx, check the installed version: npm list @typebot.io/lib or check your package.json
  3. If using Docker, check the image tag: docker images | grep typebot
  4. Upgrade to version 3.17.2 or later by updating your dependency or Docker image tag
  5. For npm installations: npm install @typebot.io/lib@latest or update version in package.json to ^3.17.2
  6. For Docker: Pull the new image with tag 3.17.2 or latest (e.g., docker pull baptistearno/typebot:3.17.2)
  7. Restart the TypeBot service to apply the update
  8. Verify the upgrade was successful by checking the running version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49213 — 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-49213 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