# CVE-2026-100685: Budibase before 3.45.0 Information Disclosure via Chat Links

> Attackers with builder access can enumerate chat identity link records across all workspaces, exposing sensitive user and service identifiers.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 26 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-76m3-47v8-p7h6, GHSA-j425-cpch-6j4p

## What is CVE-2026-100685?

CVE-2026-100685 is a high-severity missing authorization vulnerability in budibase server, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Budibase before 3.45.0 fails to properly scope the GET /api/chat-links endpoint by workspace, allowing builders to enumerate chat identity link records across all workspaces in a tenant. Attackers with builder access to a single workspace can retrieve sensitive chat identity linking data including user IDs and external chat service identifiers from other workspaces they have no permission to access.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-100685 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100685 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100685 is a high-severity missing authorization vulnerability in budibase server, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100685 exists.

Affected product: budibase server. 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-100685/ (Markdown: https://insights.sbomify.com/CVE-2026-100685/index.md)
```

## Sources

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

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