# CVE-2026-47704: Missing authorization in typebot.io

> An authenticated user can hijack another user's chatbot session by injecting arbitrary webhook data, allowing unauthorized control of the bot's execution flow.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-h67g-6q6g-58cj

## What is CVE-2026-47704?

CVE-2026-47704 is a high-severity missing authorization vulnerability in baptisteArno typebot.io, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TypeBot is a chatbot builder tool. Prior to version 3.17.0, an authenticated user who has read access to any typebot can resume a waiting webhook session that belongs to a different typebot by mixing an authorized `typebotId` and `blockId` and a foreign live `resultId`. The webhook resume handler authorizes the parent typebot first, but then resolves the descendant `result` only by `resultId`. As a result, an attacker can inject arbitrary webhook JSON into another typebot's suspended session and advance its execution without any access to the victim typebot. Version 3.17.0 patches the issue.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-47704?


## How do I fix CVE-2026-47704?

No fix has been published for CVE-2026-47704 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47704 being exploited?

There is no known exploitation of CVE-2026-47704 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47704 and fix it if it is affected.

What it is: CVE-2026-47704 is a high-severity missing authorization vulnerability in baptisteArno typebot.io, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47704 in the wild and no public exploit code.

Affected product: baptisteArno typebot.io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47704/ (Markdown: https://insights.sbomify.com/CVE-2026-47704/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47704
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47704
- OSV: https://osv.dev/vulnerability/CVE-2026-47704

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47704/
Summaries are generated and may contain mistakes; the official description above is the record.