# CVE-2026-49213: TypeBot: SSRF protection bypass via IPv6 unspecified address in Typebot HTTP request execution

> Attackers can bypass SSRF protections using IPv6 unspecified addresses to access local services via TypeBot's HTTP request features.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-qx46-p88f-xxm3

## What is CVE-2026-49213?

CVE-2026-49213 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-49213?


## How do I fix CVE-2026-49213?

No fix has been published for CVE-2026-49213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49213 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49213 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49213 and fix it if it is affected.

What it is: CVE-2026-49213 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49213 exists.

Affected product: baptisteArno typebot.io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49213/ (Markdown: https://insights.sbomify.com/CVE-2026-49213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49213
- OSV: https://osv.dev/vulnerability/CVE-2026-49213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49213/
Summaries are generated and may contain mistakes; the official description above is the record.