CVE-2026-72856: Budibase before 3.40.0 Authentication Bypass via Tenant Owner Email
Budibase versions before 3.40.0 contain an authorization/authentication bypass in the PUT /api/global/users/tenant/owner (changeTenantOwnerEmail) endpoint. On self-hosted instances (SELFHOSTED or DISABLEACCOUNTPORTAL set), the cloudRestricted middleware is a no-op and the route is protected only by a general authentication check, so any authenticated user — including a lowest-privilege BASIC app user — can reassign the tenant account-holder (top-privilege admin) email to an attacker-controlled address. The attacker can then use the public password-reset flow to take over the admin account, leading to full administrative access.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Budibaseto a version that resolves this vulnerability.Fixed in 3.40.0 - Compensating control
On self-hosted instances, restrict access to the affected endpoint PUT /api/global/users/tenant/owner (changeTenantOwnerEmail) to trusted/administrative users only (e.g., via network controls or an application gateway/WAF rule), since cloudRestricted is a no-op when SELF_HOSTED or DISABLE_ACCOUNT_PORTAL is set and the route is otherwise protected only by a general authentication check.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72856?
The severity of CVE-2026-72856 is rated high with a score of 8.1.
How do I fix CVE-2026-72856?
To fix CVE-2026-72856, upgrade Budibase to version 3.40.0 or later.
What impact does CVE-2026-72856 have on my system?
CVE-2026-72856 allows unauthorized access to change the tenant owner email on self-hosted instances.
Is CVE-2026-72856 applicable to all versions of Budibase?
CVE-2026-72856 is applicable to all versions of Budibase prior to 3.40.0.
What types of attacks can CVE-2026-72856 facilitate?
CVE-2026-72856 can facilitate unauthorized changes to user account ownership, leading to possible data compromise.