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.
CVE-2026-62865
This high-severity CVE scores 8.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(low)
- EG Risk
- 54(Attend)EG Risk 54/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026v3.18.0
Patch available: baptisteArno/typebot.io v3.18.0
https://github.com/baptisteArno/typebot.io/releases/tag/v3.18.0commit 9c81300e5abb (baptisteArno/typebot.io)
Patch available: baptisteArno/typebot.io v3.18.0 (contains commit 9c81300e5abb)
https://github.com/baptisteArno/typebot.io/commit/9c81300e5abb28a68a5af2920b92043e3512899dArbitrary server file read via Send Email attachments · Advisory · baptisteArno/typebot.io · GitHub
https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-j32h-2r6x-wmf3Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 12:34 UTCEG score recompute
- 2026-08-25 22:29 UTCEG score recompute
- 2026-08-25 22:00 UTCEG score recompute
- 2026-08-25 21:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-62865?
When was CVE-2026-62865 disclosed?
What is the CVSS score of CVE-2026-62865?
How do I remediate CVE-2026-62865?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62865
Is Your Infrastructure Affected by CVE-2026-62865?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.