# CVE-2026-62865: TypeBot: Arbitrary server file read via Send Email block attachment path

> Attackers can read arbitrary server files, including secrets, by manipulating email attachment paths in Typebot's Send Email block.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-j32h-2r6x-wmf3

## What is CVE-2026-62865?

CVE-2026-62865 is a high-severity path traversal vulnerability in baptisteArno typebot.io, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Typebot is an open-source chatbot builder. In self-hosted versions prior to 3.18.0, the server-side Send Email integration block allows arbitrary reading of local files on the server. The block builds Nodemailer attachments from a typebot variable, and its parseAttachments helper returns the supplied value as a filesystem path whenever it does not start with the application's own base URL, instead of requiring an http or https URL. The Nodemailer transport is created without disableFileAccess or disableUrlAccess, both of which default to false, so an attachment specified as an absolute server path is read from the local filesystem and delivered. Because both the attachment value and the recipient list are attacker-controllable typebot variables, any registered user can publish a bot whose Send Email block attaches an absolute path such as /etc/passwd or /proc/self/environ and mails it to an address they control. This enables reading any file the server process can access, including process environment secrets such as the credential encryption key and database connection string, without administrative privileges or victim interaction. Open signup is enabled by default and the system SMTP credential is already configured, so no non-default configuration is required. This issue is fixed in version 3.18.0.

Weakness: CWE-73 (External Control of File Name or Path), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-62865?


## How do I fix CVE-2026-62865?

No fix has been published for CVE-2026-62865 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62865 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62865 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62865 and fix it if it is affected.

What it is: CVE-2026-62865 is a high-severity path traversal vulnerability in baptisteArno typebot.io, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62865 exists.

Affected product: baptisteArno typebot.io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62865/ (Markdown: https://insights.sbomify.com/CVE-2026-62865/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62865
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62865
- OSV: https://osv.dev/vulnerability/CVE-2026-62865

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62865/
Summaries are generated and may contain mistakes; the official description above is the record.