CVE-2025-64709VulnerabilityPublished 13 Nov 2025

CVE-2025-64709: baptisteArno typebot.io · Server-Side Request Forgery (SSRF)

Affects baptisteArno typebot.ioSource CVE Database V5

Not known to be exploited · CVSS 9.6 Critical : upgrade to 3.13.1 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.6Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.13.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade baptistearno/typebot.io to 3.13.1.

Affected software

Product	Affected	Fixed in
GitHubbaptistearno/typebot.io`pkg:github/baptistearno/typebot.io`Other threats	Affected <3.13.1	Fixed in 3.13.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately upgrade Typebot deployments to version 3.13.1 or later to apply the official patch that fixes the SSRF vulnerability. 2. Restrict access to the Typebot webhook block functionality to only trusted and necessary authenticated users, minimizing the attack surface. 3. Implement strict network segmentation and egress filtering on Kubernetes nodes to prevent unauthorized outbound HTTP requests to sensitive endpoints such as the AWS IMDS. 4. Employ AWS IAM best practices by limiting the permissions of the EKS node role to the minimum necessary, reducing potential damage if credentials are compromised. 5. Monitor logs and network traffic for unusual HTTP requests originating from Typebot servers, especially those targeting IMDS endpoints. 6. Use AWS security features such as IMDSv2 enforcement and AWS Config rules to detect and prevent unauthorized metadata access. 7. Conduct regular security audits and penetration tests focusing on internal SSRF vectors and webhook components. 8. Educate developers and administrators about the risks of SSRF and secure coding practices related to HTTP request handling within chatbot or webhook services.

Description

Typebot is an open-source chatbot builder. In versions prior to 3.13.1, a Server-Side Request Forgery (SSRF) vulnerability in the Typebot webhook block (HTTP Request component) functionality allows authenticated users to make arbitrary HTTP requests from the server, including access to AWS Instance Metadata Service (IMDS). By bypassing IMDSv2 protection through custom header injection, attackers can extract temporary AWS IAM credentials for the EKS node role, leading to complete compromise of the Kubernetes cluster and associated AWS infrastructure. Version 3.13.1 fixes the issue.

Impact

For European organizations leveraging Typebot in AWS EKS environments, this vulnerability poses a severe risk. Successful exploitation can lead to unauthorized access to sensitive cloud infrastructure, including Kubernetes clusters and AWS resources. This compromises confidentiality by exposing sensitive data and credentials, integrity by allowing attackers to manipulate workloads or configurations, and availability if attackers disrupt services or deploy malicious workloads. The breach of AWS IAM credentials can facilitate lateral movement across cloud services, increasing the attack surface. Organizations in sectors with stringent data protection requirements (e.g., finance, healthcare, government) face regulatory and reputational damage if exploited. The requirement for authentication limits exposure to internal or trusted users, but insider threats or compromised credentials can still trigger exploitation. The lack of user interaction needed means automated attacks are feasible once authenticated access is gained. Overall, the vulnerability threatens cloud security posture and operational continuity for European enterprises using vulnerable Typebot versions.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/baptisteArno/typebot.io/security/advisories/GHSA-8gq9-rw7v-3jpr (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2025, 20:05 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats