# CVE-2026-72849: Budibase before 3.40.0 Identity Confusion via Chat-Link Handoff CSRF

> Attackers can use CSRF to bind their chat identity to a victim's account, enabling impersonation and permission inheritance in Budibase.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-4q4m-8h83-fcmr, GHSA-pvcr-8mvp-w8qr

## What is CVE-2026-72849?

CVE-2026-72849 is a high-severity vulnerability in budibase server, published on 13 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Budibase before 3.40.0 contains a cross-site request forgery vulnerability in the chat-link handoff endpoint that allows attackers to bind an external chat identity to a victim's account. Attackers can craft a phishing page that auto-submits a POST request with a leaked confirmation token to bind their chat identity to a victim user's account, enabling impersonation within agent operations and inheritance of victim permissions.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

2 open source packages ship an affected version, including @budibase/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@budibase/server` | npm | All versions to 3.38.1 | None |
| `@budibase/server` | npm | All versions to 3.38.1 | None |

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

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

## Is CVE-2026-72849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72849 is a high-severity vulnerability in budibase server, published on 13 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-72849 in the wild and no public exploit code.

Affected packages and fixed versions:
- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed
- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed

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-72849/ (Markdown: https://insights.sbomify.com/CVE-2026-72849/index.md)
```

## Sources

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

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