Skip to main content
VulnerabilityPublished

CVE-2026-48763: baptisteArno typebot.io · Missing Authorization

Affects baptisteArno typebot.ioSource CVE Database V5

0
Compare

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

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% 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:N/UI:N/S:U/C:N/I:H/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 8 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

Version 3.17.0 of TypeBot fixes this vulnerability by removing or securing the deprecated public upload endpoint. Since TypeBot is a cloud service, the vendor manages remediation server-side. Users should ensure they are using version 3.17.0 or later. Patch status is confirmed as fixed in 3.17.0.

Description

TypeBot is a chatbot builder tool. Versions prior to 3.17.0 expose a deprecated public upload endpoint at `GET /api/v1/typebots/{typebotId}/blocks/{blockId}/storage/upload-url` that accepts an attacker-controlled `filePath` and returns a presigned S3 `PUT` URL for that exact key. Because the endpoint only checks that the referenced typebot is public and that the referenced block is a file input block, an unauthenticated attacker who knows a valid public `typebotId` and `blockId` can request presigned upload URLs for arbitrary objects in the shared bucket, including `private/...` and other tenants' `public/...` paths. Version 3.17.0 fixes this issue.

References

Community reviews

Loading reviews…