CVE-2026-47702
TypeBot stores API tokens in cleartext allowing token theft and full impersonation.
Is CVE-2026-47702 being exploited?
Not confirmed. CVE-2026-47702 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-47702?
CVE-2026-47702 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47702?
Yes. A fix has been recorded for CVE-2026-47702. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47702 affect?
CVE-2026-47702 affects TypeBot 3.16.1, Self-hosted TypeBot instances storing DB, Deployments using embedded API tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47702?
Upgrade to TypeBot 3.17.0 and rotate/revoke all API tokens immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers with DB read access (SQLi, backup exposure, insider) can extract bearer tokens and impersonate any user, bypassing passwords and MFA.
Immediate action required
- affected= 3.16.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.