dbcve.org
TypebotApplication

CVE-2025-64709

CRITICAL · 9.9 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 3.13.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Typebot versions before 3.13.1 contain an SSRF vulnerability in the webhook block HTTP Request component, allowing authenticated users to make arbitrary server-side HTTP requests. Attackers exploit this to access AWS Instance Metadata Service (IMDS), bypassing IMDSv2 protections via custom header injection to extract temporary IAM credentials for the EKS node role, achieving full Kubernetes cluster and AWS infrastructure compromise.

MitigationUpgrade to Typebot version 3.13.1 or later immediately, rotate all potentially exposed AWS credentials, and implement IMDSv2 token requirement protections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TypebotApplication
Affected:< 3.13.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Typebot installation and version
    Locate the Typebot installation and check the version number against the software's version file or admin interface. Common locations include package.json, docker image tags, or the /api/health or /admin/settings endpoints.
    Affected if The installed version of Typebot is below 3.13.1
  2. Confirm webhook block is accessible to authenticated users
    Review Typebot's user role permissions and bot builder configuration to determine if the HTTP Request block in webhooks can be configured by non-admin users.
    Affected if Authenticated users (especially non-admin) can create or modify webhook blocks with custom URLs
  3. Check for outbound HTTP request logging or network monitoring
    Review HTTP access logs, proxy logs, or network flow data for requests originating from the Typebot server to AWS IMDS endpoints (169.254.169.254) or internal infrastructure.

You are affected if you run Typebot version below 3.13.1 and have authenticated users who can access the webhook HTTP Request component, as the SSRF vulnerability allows them to reach AWS IMDS and extract credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.13.1 or later
Fixed in 3.13.1
Interim mitigation

Upgrade to Typebot version 3.13.1 or later immediately, rotate all potentially exposed AWS credentials, and implement IMDSv2 token requirement protections.

Recommended fix High confidence

3.13.1

  1. Identify the current Typebot version running in your environment
  2. Review the Typebot 3.13.1 release notes for any required migration steps or configuration changes
  3. Backup the current database and configuration files
  4. Upgrade Typebot to version 3.13.1 or later using your deployment method (e.g., Docker, npm, or your existing installation mechanism)
  5. Verify the upgrade was successful by checking the Typebot version
  6. Restart all Typebot services to ensure the patched version is fully deployed
  7. Validate that the HTTP Request/webhook block functionality works as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Typebot Scoped from the published advisory
  • Consultation10.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,460
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data