dbcve.org
CWE-915Weakness · CWE-915

CVE-2026-48150

CRITICAL · 9.0 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Budibase is an open-source low-code platform. Prior to 3.39.0, /api/public/v1/roles/assign is guarded by the builderOrAdmin middleware, which passes any user who is a builder for the app id in the x-budibase-app-id header. That check admits both global builders and workspace-scoped builders (builder.apps set but builder.global unset). The controller then spreads the request body into the SDK call, and the SDK grants builder.global=true or admin.global=true on whichever user ids the caller supplies. Bob, a workspace-scoped builder with an API key, promotes himself or any other user to global admin with one POST. The whole flow is tenant-wide privilege escalation from an app-level role, available to anyone with an Enterprise license that unlocks the EXPANDED_PUBLIC_API feature. This vulnerability is fixed in 3.39.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Budibase versions prior to 3.39.0, the /api/public/v1/roles/assign endpoint uses a builderOrAdmin middleware that incorrectly grants access to workspace-scoped builders (users with builder.apps set but without builder.global=true). The endpoint then spreads the request body into an SDK call without validating the user-supplied IDs, allowing the SDK to grant elevated global privileges (builder.global=true or admin.global=true) to any user ID provided. A workspace-scoped builder with an Enterprise license and EXPANDED_PUBLIC_API feature can exploit this to achieve tenant-wide privilege escalation to global admin.

MitigationUpgrade Budibase to version 3.39.0 or later, which properly validates user credentials in the middleware and prevents unauthorized privilege escalation through the role assignment endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Check the installed Budibase version through the admin UI (usually in Settings > About) or by querying the internal /api/global/brand endpoint
    Affected if The installed version is prior to 3.39.0
  2. Confirm workspace-scoped builders exist
    Query the users API or check user role configurations to identify accounts where builder.apps is set but builder.global is unset
    Affected if There are users with workspace-scoped builder permissions (builder.apps populated, builder.global not set)
  3. Check for API key access
    Review whether workspace-scoped builders have been issued API keys, which are required to make API calls to the vulnerable endpoint
    Affected if Workspace-scoped builders possess valid API keys
  4. Verify endpoint accessibility
    Attempt a test request to /api/public/v1/roles/assign (or check server logs for access to this endpoint) to confirm the endpoint is reachable from the API
    Affected if The /api/public/v1/roles/assign endpoint is exposed and accessible to workspace-scoped builders with API keys

A user is affected if their Budibase installation is version prior to 3.39.0 AND contains workspace-scoped builders with API keys who can access the /api/public/v1/roles/assign endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.39.0 or later, which properly validates user credentials in the middleware and prevents unauthorized privilege escalation through the role assignment endpoint.

Recommended fix High confidence

3.39.0

  1. Upgrade Budibase to version 3.39.0 or later
  2. After upgrade, verify that the /api/public/v1/roles/assign endpoint properly validates permissions and no longer allows workspace-scoped builders to grant global admin/global builder privileges
  3. Confirm the builderOrAdmin middleware now correctly distinguishes between global and workspace-scoped builders for this endpoint

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data