Skip to main content
VulnerabilityPublished

CVE-2026-47702: baptisteArno typebot.io · Cleartext Storage of Sensitive Information

Affects baptisteArno typebot.ioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 3.17.0 : patch baptisteArno typebot.io as a priority.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.17.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
baptisteArnotypebot.ioAffected
  • =3.16.1
Fixed in–
GitHubbaptistearno/typebot.iopkg:github/baptistearno/typebot.ioOther threatsAffected
  • =3.16.1
Fixed in–

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

AI-suggested

Upgrade to TypeBot version 3.17.0 or later, where the cleartext storage of API tokens has been fixed. Until the upgrade, restrict database read access to trusted personnel only and monitor for any unauthorized access attempts. Patch status is not explicitly confirmed in the vendor advisory, but the description states version 3.17.0 fixes the issue.

Description

TypeBot is a chatbot builder tool. In version 3.16.1, API tokens (bearer credentials used to authenticate against the builder API) are stored in the database as cleartext strings. An attacker who gains read access to the database (e.g., via SQL injection, backup exposure, or insider access) can extract all API tokens and impersonate any user without requiring a password or multi-factor authentication. Version 3.17.0 fixes the issue.

References

Community reviews

Loading reviews…