Critical · published November 14, 2025
🚨 A crafty webhook in Typebot is your weakest link! With just a bit of trickery, authenticated users can exploit this SSRF flaw to launch arbitrary HTTP requests straight from your server. 🔥 Think of it as a delivery person who can not only drop off packages but also access your private vault while they’re at it. If they bring a special request slip, they can peek into everything locked away, including your AWS secrets! If an attacker exploits this vulnerability, they could waltz right into your Kubernetes cluster. This means they can snatch temporary AWS IAM credentials and gain full control over your AWS infrastructure — an absolutely devastating scenario for any organization!
Think of it as a delivery person who can not only drop off packages but also access your private vault while they’re at it. If they bring a special request slip, they can peek into everything locked away, including your AWS secrets! In versions prior to 3.13.1, an SSRF vulnerability in Typebot allows authenticated users to bypass IMDSv2 protections through custom header injection, exposing sensitive AWS instance metadata to attackers via arbitrary HTTP requests.
If an attacker exploits this vulnerability, they could waltz right into your Kubernetes cluster. This means they can snatch temporary AWS IAM credentials and gain full control over your AWS infrastructure — an absolutely devastating scenario for any organization! To safeguard your infrastructure, update Typebot immediately to version 3.13.1. Additionally, review your webhook configurations and restrict access to sensitive metadata services. Don't forget to monitor your cluster for any unusual activities! You've got this! Follow these steps to lock down your Kubernetes environment and keep those secrets safe! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| typebot/typebot | < 3.13.1 | 3.13.1 |