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.
CVE-2026-49213
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EPSS
- 23.9%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026SSRF protection bypass via IPv6 unspecified address in Typebot HTTP request execution · Advisory · baptisteArno/typebot.io · GitHub
https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-qx46-p88f-xxm3v3.17.2
Patch available: baptisteArno/typebot.io v3.17.2
https://github.com/baptisteArno/typebot.io/releases/tag/v3.17.2🐛 Block IPv6 unspecified SSRF targets
Patch available: baptisteArno/typebot.io v3.17.2 (PR #2511 merged 2026-05-24)
https://github.com/baptisteArno/typebot.io/pull/2511commit f56c3c3f771d (baptisteArno/typebot.io)
Patch available: baptisteArno/typebot.io v3.17.2 (contains commit f56c3c3f771d)
https://github.com/baptisteArno/typebot.io/commit/f56c3c3f771df13a8c11e88f500dfdd78981bed1Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-14 00:26 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 12:01 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 23:36 UTCEG score recompute
- 2026-07-12 11:10 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 22:43 UTCEG score recompute
- 2026-07-11 10:18 UTCEG score recompute
- 2026-07-10 21:53 UTCEG score recompute
- 2026-07-10 21:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-49213?
When was CVE-2026-49213 disclosed?
Is CVE-2026-49213 actively exploited?
What is the CVSS score of CVE-2026-49213?
How do I remediate CVE-2026-49213?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-49213
Is Your Infrastructure Affected by CVE-2026-49213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.