Skip to main content
Vulnerability Database/CVE-2026-100685

CVE-2026-100685: Budibase Information Disclosure Flaw

CVE-2026-100685 is an information disclosure vulnerability in Budibase that exposes chat identity data across workspaces. Builders can access sensitive user IDs and chat identifiers from unauthorized workspaces.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100685 Overview

CVE-2026-100685 is an authorization flaw in Budibase versions prior to 3.45.0. The GET /api/chat-links endpoint fails to scope results by workspace. A builder with access to any single workspace can enumerate chat identity link records across every workspace in the tenant. Exposed data includes user IDs and external chat service identifiers belonging to workspaces the attacker is not authorized to access. The issue is tracked as CWE-863: Incorrect Authorization and documented in GitHub Security Advisory GHSA-76m3-47v8-p7h6.

Critical Impact

Any authenticated builder in a Budibase tenant can retrieve chat identity link records (user IDs and external chat service identifiers) from every workspace in that tenant, breaking workspace isolation.

Affected Products

  • Budibase versions prior to 3.45.0
  • Self-hosted and cloud Budibase tenants with multi-workspace configurations
  • Deployments using the chat identity linking feature exposed via /api/chat-links

Discovery Timeline

  • 2026-09-26 - CVE-2026-100685 published to the National Vulnerability Database
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-100685

Vulnerability Analysis

Budibase is a low-code platform that organizes resources into tenants and workspaces. Builders operate within specific workspaces and should only see data scoped to those workspaces. The GET /api/chat-links endpoint returns chat identity link records that associate Budibase users with external chat service identifiers. The endpoint enforces authentication and builder-role checks but omits the workspace filter when retrieving records. As a result, the handler returns all chat link records in the tenant regardless of the requester's workspace membership. This is a broken access control defect classified under CWE-863.

Root Cause

The root cause is a missing authorization scope on the /api/chat-links route handler. The query that fetches chat link records does not include a workspace predicate, and the response layer does not filter records against the caller's workspace permissions. The authorization check validates role (builder) but not resource ownership. Version 3.45.0 adds the workspace scoping condition on both the data query and the response path.

Attack Vector

An attacker needs valid credentials for a builder account in any workspace within a target tenant. The attacker issues an authenticated HTTP GET request to /api/chat-links on the Budibase instance. The response contains the full list of chat identity link records across every workspace in the tenant. The attacker extracts user IDs and external chat service identifiers from workspaces where they have no legitimate access. The attack requires no user interaction and leaves standard application logs showing a routine API call from an authorized builder session.

No verified public exploit code is available. See the Vulncheck advisory for Budibase and the GitHub Security Advisory GHSA-76m3-47v8-p7h6 for additional technical context.

Detection Methods for CVE-2026-100685

Indicators of Compromise

  • Unexpected GET requests to /api/chat-links from builder accounts that do not use the chat linking feature
  • Builder sessions issuing /api/chat-links calls followed by access to user IDs or external identifiers from workspaces they do not own
  • Spikes in response size on /api/chat-links indicating cross-workspace enumeration

Detection Strategies

  • Review application and reverse-proxy logs for GET /api/chat-links requests and correlate the requester's workspace membership against the record counts returned
  • Alert on builder accounts querying /api/chat-links outside their normal usage baseline
  • Inspect Budibase audit logs for builder actions on resources that cross workspace boundaries after a /api/chat-links request

Monitoring Recommendations

  • Forward Budibase application logs and HTTP access logs to a centralized SIEM for retention and correlation
  • Create detections that flag any single session enumerating /api/chat-links repeatedly or returning record counts larger than the requester's workspace scope
  • Track builder-role account creation and privilege changes to limit the pool of accounts able to call this endpoint

How to Mitigate CVE-2026-100685

Immediate Actions Required

  • Upgrade all Budibase instances to version 3.45.0 or later
  • Audit builder-role accounts across every workspace and revoke access that is no longer required
  • Rotate any external chat service identifiers that may have been exposed to unauthorized builders
  • Review historical access logs for /api/chat-links requests predating the upgrade

Patch Information

Budibase addressed the issue in version 3.45.0 by adding workspace scoping to the /api/chat-links endpoint. The fix is documented in GitHub Security Advisory GHSA-76m3-47v8-p7h6. Operators running self-hosted deployments should pull the patched release and redeploy. Cloud-hosted tenants should confirm with Budibase that the upgrade has been applied.

Workarounds

  • Restrict network access to the Budibase management API using a reverse proxy or Web Application Firewall rule that blocks /api/chat-links until the upgrade is complete
  • Temporarily reduce the number of builder-role accounts to the minimum operationally required
  • Disable or avoid use of the chat identity linking feature until patched versions are deployed
bash
# Example reverse-proxy rule (nginx) to block the vulnerable endpoint pre-patch
location = /api/chat-links {
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.