CVE-2026-100687 budibase CVE debrief

Who should care

Budibase Server administrators and users with Builder access should assess exposure and prioritize updating to version 3.45.0 or later to prevent credential exposure. They should also review and redact plaintext datasource credentials, monitor for suspicious table save or delete operations, and track exceptions and retest remediated assets.

Why it matters

Defenders should prioritize verifying Budibase Server versions and updating to 3.45.0 or later to prevent credential exposure. Budibase Server administrators and users with Builder access should assess exposure and take action to prevent unauthorized access.

• Verify Budibase Server versions to determine exposure
• Update to version 3.45.0 or later to prevent credential exposure
• Monitor for suspicious table save or delete operations to detect potential exploitation
• Review and redact plaintext datasource credentials to prevent unauthorized access

Technical summary

Budibase Server before 3.45.0 fails to redact plaintext datasource credentials before broadcasting external table updates to the Builder collaboration websocket room. Attackers with Builder access can intercept unredacted datasource objects containing database passwords and API keys by observing table save or delete operations. The vulnerability is highly severe, with a CVSS score of 7, and defenders should prioritize verifying Budibase Server versions and updating to 3.45.0 or later to prevent credential exposure.

Defensive priority

Defenders should prioritize verifying Budibase Server versions and updating to 3.45.0 or later to prevent credential exposure.

Recommended defensive actions

• Verify Budibase Server versions and update to 3.45.0 or later
• Review and redact plaintext datasource credentials
• Monitor for suspicious table save or delete operations
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, limited information is available on potential exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.