Skip to main content
VulnerabilityPublished Updated

CVE-2026-48766: baptisteArno typebot.io · Information Exposure

Affects baptisteArno typebot.ioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 3.17.0 soon.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 10 Nov 2026.

What to do

Upgrade typebot.io and baptistearno/typebot.io to 3.17.0.

Affected software

ProductAffectedFixed in
baptisteArnotypebot.ioAffected
  • <3.17.0
Fixed in
  • 3.17.0
GitHubbaptistearno/typebot.iopkg:github/baptistearno/typebot.ioOther threatsAffected
  • <3.17.0
Fixed in
  • 3.17.0

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

AI-suggested

Upgrade TypeBot to version 3.17.0 or later, where this vulnerability is patched. No other mitigation or temporary workaround is indicated in the available data.

Description

TypeBot is a chatbot builder tool. Versions prior to 3.17.0 allow a low-privilege guest member of a workspace to exfiltrate stored OpenAI-compatible API keys by invoking the OpenAI model-listing helper with an attacker-controlled `baseUrl`. The vulnerable path decrypts the selected workspace credential, creates an OpenAI client with the secret in both `apiKey` and the explicit `api-key` header, and then sends the outbound request to the caller-supplied URL. Because the permission check accepts any readable workspace member and `listCredentials` reveals credential identifiers to guests, a guest can force the server to deliver the workspace secret to attacker infrastructure. Version 3.17.0 patches the issue.

References

Community reviews

Loading reviews…