CVE-2026-48764: CWE-918: Server-Side Request Forgery (SSRF) in baptisteArno typebot.io
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.
AI Analysis
Technical Summary
TypeBot.io versions before 3.17.2 implement SSRF validation by resolving a hostname once and checking if the resolved IP is in a forbidden range. However, the actual outbound request performs a fresh DNS resolution without pinning the IP to the validated address, creating a TOCTOU gap. An attacker can exploit this by supplying a URL that passes initial validation but resolves to internal or metadata IPs at request time via DNS rebinding. This enables unauthorized server-side access to internal HTTP services, cloud metadata endpoints, and potentially sensitive internal resources. The vulnerability is identified as CWE-918 and has a CVSS 3.1 score of 8.2 (high severity). It is fixed in version 3.17.2.
Potential Impact
Successful exploitation allows an attacker to bypass SSRF protections and make the server perform HTTP requests to internal network services or cloud metadata endpoints. This can lead to disclosure of sensitive metadata, access to internal admin panels, credential theft, and further internal compromise. The impact depends on the internal services accessible from the server but includes high confidentiality risk and potential privilege escalation.
Mitigation Recommendations
Upgrade TypeBot to version 3.17.2 or later, where this SSRF vulnerability is fixed. Patch status is not explicitly stated beyond the fix in 3.17.2, so applying this update is the recommended remediation. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.
CVE-2026-48764: CWE-918: Server-Side Request Forgery (SSRF) in baptisteArno typebot.io
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.
CVSS v3.1
Score 8.2high
Affected software
pkg:github/baptistearno/typebot.ioRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
TypeBot.io versions before 3.17.2 implement SSRF validation by resolving a hostname once and checking if the resolved IP is in a forbidden range. However, the actual outbound request performs a fresh DNS resolution without pinning the IP to the validated address, creating a TOCTOU gap. An attacker can exploit this by supplying a URL that passes initial validation but resolves to internal or metadata IPs at request time via DNS rebinding. This enables unauthorized server-side access to internal HTTP services, cloud metadata endpoints, and potentially sensitive internal resources. The vulnerability is identified as CWE-918 and has a CVSS 3.1 score of 8.2 (high severity). It is fixed in version 3.17.2.
Potential Impact
Successful exploitation allows an attacker to bypass SSRF protections and make the server perform HTTP requests to internal network services or cloud metadata endpoints. This can lead to disclosure of sensitive metadata, access to internal admin panels, credential theft, and further internal compromise. The impact depends on the internal services accessible from the server but includes high confidentiality risk and potential privilege escalation.
Mitigation Recommendations
Upgrade TypeBot to version 3.17.2 or later, where this SSRF vulnerability is fixed. Patch status is not explicitly stated beyond the fix in 3.17.2, so applying this update is the recommended remediation. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-22T19:39:05.356Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3332cbf198dc38c133d861
Added to database: 06/17/2026, 23:50:35 UTC
Last enriched: 06/18/2026, 00:05:03 UTC
Last updated: 07/13/2026, 19:47:38 UTC
Views: 86
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.