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-100687 Overview
Budibase Server versions before 3.45.0 leak plaintext datasource credentials through the Builder collaboration websocket. The server fails to redact sensitive fields before broadcasting external table update events to the Builder room. Attackers with Builder access can intercept unredacted datasource objects by observing routine table save or delete operations. The exposed data includes database passwords and API keys used to connect Budibase to external systems. This is an information disclosure flaw tracked under CWE-200.
Critical Impact
Authenticated Builder users can harvest plaintext database passwords and API keys for every external datasource configured in the Budibase workspace.
Affected Products
- Budibase Server versions prior to 3.45.0
- Self-hosted Budibase deployments exposing the Builder interface
- Multi-tenant Budibase instances with shared Builder access
Discovery Timeline
- 2026-09-26 - CVE-2026-100687 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100687
Vulnerability Analysis
Budibase uses a websocket-based collaboration layer that mirrors Builder state changes across connected clients. When a user saves or deletes an external table, the server emits an update event containing the full datasource object. The datasource object includes the connection configuration used to reach external databases and third-party APIs.
The server-side broadcast path omits the credential-redaction step applied in REST responses. As a result, every client subscribed to the Builder room receives the raw configuration, including fields such as database passwords, connection strings, and API keys. The exposure is passive and triggers on normal Builder activity rather than crafted requests.
Exploitation requires authenticated Builder access, which maps to the high privileges-required rating in the CVSS vector. The attack vector is network based and does not require user interaction once the attacker is connected to the websocket room.
Root Cause
The root cause is missing output sanitization on the websocket broadcast handler for external table events. The REST API layer strips sensitive datasource fields before serialization, but the collaboration channel reuses the in-memory datasource object directly. This inconsistency between transport layers results in the credential leak described in the GitHub Security Advisory GHSA-rmv5-3xpj-w885.
Attack Vector
An attacker with any Builder role connects to the Budibase Builder websocket room for a target workspace. The attacker then waits for another user, or triggers themselves, a table save or delete action on an external datasource. The server broadcasts the datasource payload with credentials in cleartext. The attacker captures the message and extracts the credentials for lateral movement into the backing database or SaaS API. See the VulnCheck advisory for additional detail.
No verified public exploit code is available. The vulnerability is described in prose in the referenced advisories.
Detection Methods for CVE-2026-100687
Indicators of Compromise
- Unexpected websocket subscriptions to the Builder collaboration room from accounts that do not normally edit tables.
- Outbound connections from Builder accounts to external databases or APIs using credentials that were only configured within Budibase.
- Credential reuse alerts from backing databases showing logins from new source IPs tied to Builder users.
Detection Strategies
- Inspect Budibase application logs for table:save and table:delete broadcast events and correlate them with the roster of connected websocket clients.
- Review access logs for Builder role assignments granted shortly before a burst of table edit events.
- Monitor backing datasources for authentication from IP addresses not associated with the Budibase host.
Monitoring Recommendations
- Enable audit logging for Builder role changes and websocket session establishment on the Budibase server.
- Forward Budibase logs to a central analytics platform to baseline normal table edit activity and alert on anomalies.
- Rotate datasource credentials on a scheduled cadence and alert on usage of retired credentials.
How to Mitigate CVE-2026-100687
Immediate Actions Required
- Upgrade Budibase Server to version 3.45.0 or later on all self-hosted deployments.
- Rotate every datasource credential, database password, and API key configured in affected Budibase workspaces.
- Audit the list of accounts holding Builder access and revoke roles that are not strictly required.
- Review websocket and application logs for prior table save or delete events that may have exposed credentials.
Patch Information
The fix is included in Budibase Server 3.45.0. The patched release redacts sensitive datasource fields before broadcasting external table events to the Builder collaboration room. Patch details are published in the GitHub Security Advisory GHSA-rmv5-3xpj-w885.
Workarounds
- Restrict Builder role assignments to a minimal, trusted set of administrators until the upgrade is complete.
- Place the Budibase Builder interface behind a VPN or identity-aware proxy to limit network exposure of the websocket endpoint.
- Avoid making external table edits in shared workspaces on vulnerable versions, since each edit broadcasts the credentials.
# Configuration example: upgrade self-hosted Budibase via Docker
docker pull budibase/budibase:3.45.0
docker stop budibase && docker rm budibase
docker run -d --name budibase -p 10000:80 \
-v budibase_data:/data \
budibase/budibase:3.45.0
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

