Quick answers
- Is CVE-2026-62865 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62865 being exploited in the wild.
- How severe is CVE-2026-62865?
- Informational severity, with a CVSS score of 7.5, published 25 August 2026.
- Which products and versions are affected?
- Typebot prior to 3.18.0.
- Is there a fix for CVE-2026-62865?
- A patch was published on 2026-06-27: Fix commit merged; version 3.18.0 released 2026-08-21 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62865 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-62865?
- Check whether you run Typebot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a local file read in the Send Email integration block caused by insecure attachment handling. The parseAttachments helper treats any non-HTTP URL as a filesystem path and passes it directly to Nodemailer without enabling file access restrictions (disableFileAccess and disableUrlAccess both default to false). An attacker can create a typebot with a Send Email block that attaches an absolute path like /etc/passwd or /proc/self/environ, then trigger the block to send the file to an attacker-controlled email address. Since both the attachment path and recipient email are typebot variables under attacker control, and open signup is enabled by default, no authentication or administrative privileges are required. The fix in version 3.18.0 restricts attachments to valid Typebot upload URLs, enables Nodemailer file access protection, and requires short-lived storage URLs for private uploads.
Affected products
- Typebot Typebot prior to 3.18.0
Timeline
- 2026-08-25: disclosed
- 2026-06-27: patched: Fix commit merged; version 3.18.0 released 2026-08-21