CVE-2026-48764 TypeBot has SSRF in HTTP request and script fetch flows via DNS rebinding bypass

High 8.2 Published Updated

Attacker can bypass SSRF protections via DNS rebinding to access internal services and cloud metadata.

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

What is CVE-2026-48764?

CVE-2026-48764 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

TypeBot is a chatbot builder tool. In versions prior to 3.17.2, SSRF validation is implemented by resolving a hostname once and checking whether the resolved IP belongs to a forbidden range allowing for DNS rebinding bypass. The root cause is a time-of-check to time-of-use gap in the SSRF guard. The validator resolves the hostname and approves it, but the later request path performs a fresh resolution and connects to whatever IP the hostname maps to at that moment. The actual outbound request is then performed later using the original hostname, without pinning the validated IP to the network connection. An attacker who can supply a URL to a public bot that performs a server-side HTTP Request block or server-side script fetch can use DNS rebinding to pass the initial validation and still force the server to connect to a private or metadata address during the real request. This enables server-side access to private network services, cloud metadata endpoints, and other internal HTTP targets that the validator was intended to block. The exact downstream impact depends on the reachable internal services. Concrete consequences include metadata disclosure, access to internal admin panels, credential theft from metadata services, and further compromise through internal-only HTTP interfaces. This issue has been fixed in version 3.17.2.

Weakness: CWE-918

Which versions are affected by CVE-2026-48764?

How do I fix CVE-2026-48764?

No fix has been published for CVE-2026-48764 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-48764 being exploited?

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

Sources

Also known as GHSA-hgqq-whf5-mrrf.

Is CVE-2026-48764 in your software?

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

Check your SBOMs for free