CVE-2026-34207 TypeBot: SSRF Protection Bypass via DNS-Resolved Hostnames in Webhook / HTTP Request Validation

High 7.6 Published Updated

Attackers can bypass SSRF protections in TypeBot by using hostnames that resolve to internal IPs, allowing access to cloud metadata and private networks.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-34207?

CVE-2026-34207 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 22 May 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. In versions prior to 3.16.0, SSRF protection for Webhook / HTTP Request blocks validates only the URL string, blocked hostname literals, and literal IP formats. It does not resolve DNS before allowing the request. As a result, a hostname such as ssrf-repro.example that resolves to 127.0.0.1, 169.254.169.254, or RFC1918/private space passes validation and is later fetched by the backend HTTP client. This enables server-side request forgery to loopback, cloud metadata, and private network targets. This issue has been resolved in version 3.16.0.

Weakness: CWE-918, CWE-20

Which versions are affected by CVE-2026-34207?

How do I fix CVE-2026-34207?

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

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-34207 being exploited?

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

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-grcc-6x37-wwgp.

Is CVE-2026-34207 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free