Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Budibase Single-Tenant Bootstrap Bypass (CVE-2026-122247)

CVE-2026-122247 is an authentication and authorization flaw in self-hosted, single-tenant Budibase.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-122247
Vendor
Budibase
Affected Product
Budibase self-hosted single-tenant deployment
Exploitation
Not confirmed
Published
2026-11-20

An unauthenticated network attacker can bypass the one-time setup guard by making it check an unused tenant context. Budibase's advisory was published on 10 November 2026; the CVE record was published on 20 November.The result is persistent creation of a tenant database and a global administrator record. Repeated database creation can exhaust CouchDB resources. The researcher's test did not show access to the existing default tenant while multi-tenancy stayed disabled, so the record should not be read as a demonstrated takeover of that tenant.

What it allows

How Does CVE-2026-122247 Bypass Bootstrap Protection?

Budibase's public setup function checks whether a user already exists in the current tenant database. On a single-tenant installation, the check should protect the established default tenant. The advisory shows that a supplied tenant identifier can instead direct that check to an unused database, where no user exists.

The setup function can then create a new tenant database and global administrator document without an authenticated session. Repeating that write can consume CouchDB storage and related resources. The created account remains outside the normal default-tenant login path while multi-tenancy is disabled, according to the advisory's test.

Those records may become relevant if an operator later enables multi-tenancy or performs a tenant-aware restore or migration. That is a conditional risk described by the CVE record, not a confirmed compromise. CISA's KEV catalog version 2026.11.20 did not list this CVE.

The CVE identification guide explains how to track a specific record. The Vulnerability Intelligence platform is the relevant product page for prioritizing this software flaw.

Who is affected

Which Budibase Deployments Need Review?

The advisory describes self-hosted Budibase installations running in single-tenant mode with the worker API reachable through the front end. The CVE record identifies versions before 3.50.0 as affected. The current advisory's package field says versions below 4.0.0 are affected and lists 4.0.0 as patched.

These published ranges differ for the 3.50.x branch. The CVE description explicitly names 3.50.0 and 4.0.0 as fixed, and the referenced fix commit precedes both release tags. Record the running build, deployment mode and network reachability, then confirm the fix with Budibase before treating any 3.50.x build as cleared.

Where a self-hosted instance is exposed, restrict untrusted network access to its administration and setup functions while the version is checked. Review CouchDB database growth and unexpected tenant administrator records against authorized provisioning activity. This is our defensive triage advice, not a Budibase detection signature. The patch management process should include a running-version check after the update.

Timeline

  1. 2026-09-16

    Budibase's referenced fix commit was recorded in the repository; its history precedes both cited release tags.

  2. 2026-10-19

    Budibase published the v3.50.0 release tag.

  3. 2026-11-10

    Budibase published the GitHub advisory and v4.0.0 release tag.

  4. 2026-11-20

    The CVE Program published CVE-2026-122247; CISA KEV catalog version 2026.11.20 did not list it.

What to do

  1. Inventory self-hosted single-tenant instances

    Record each running Budibase build, whether multi-tenancy is disabled, and whether the worker API is reachable from untrusted networks.

  2. Confirm the applicable fixed release

    Budibase's CVE description names 3.50.0 and 4.0.0 as fixed, while the advisory package table lists only 4.0.0. Confirm a 3.50.x build with Budibase before marking it fixed.

  3. Update and verify the running build

    Apply a Budibase release confirmed to contain the fix. After restart, verify the reported running version and deployment mode on each instance.

  4. Review datastore and tenant changes

    Compare CouchDB database growth and tenant administrator records with authorized setup activity. Investigate unexplained records before enabling multi-tenancy or restoring tenant data.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-122247 give access to the existing default tenant?

The advisory's test did not show that outcome while multi-tenancy was disabled. It did show persistent database and administrator-record creation in another tenant context.

Which Budibase version fixes CVE-2026-122247?

The CVE description names 3.50.0 and 4.0.0. The advisory package table lists only 4.0.0, so confirm the fix in a 3.50.x build with Budibase.

What should an operator check first?

Identify self-hosted single-tenant instances, their running versions and network reachability. Then compare unexpected tenant databases and administrator records with authorized provisioning.

Sources

  1. Budibase Bootstrap Tenant-Confusion AdvisoryBudibase on GitHub
  2. CVE-2026-122247 RecordCVE Program
  3. Budibase v3.50.0 ReleaseBudibase
  4. Budibase v4.0.0 ReleaseBudibase
  5. CISA Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →