Quick answers
- Is CVE-2026-48150 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48150 being exploited in the wild.
- How severe is CVE-2026-48150?
- Critical severity, with a CVSS score of 9, published 27 May 2026.
- Which products and versions are affected?
- @budibase/server (npm) < 3.39.0, SEMVER:introduced=0,fixed=3.39.0.
- Is there a fix for CVE-2026-48150?
- Yes. @budibase/server (npm): upgrade to 3.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48150 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48150?
- Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @budibase/server (npm): upgrade to 3.39.0 or later
npm install @budibase/server@3.39.0
Technical details
A privilege escalation vulnerability exists in the `/api/public/v1/roles/assign` endpoint of Budibase. The endpoint is protected by the `builderOrAdmin` middleware, which incorrectly allows workspace-scoped builders (users restricted to specific apps) to access the role assignment logic. The underlying SDK implementation fails to verify if the caller possesses the permissions they are attempting to grant. Consequently, an attacker with a workspace-scoped builder role and an API key can perform a mass-assignment attack to set `builder.global` or `admin.global` to true for any user ID, including their own. This issue is present in versions prior to 3.39.0 and requires the Enterprise 'EXPANDED_PUBLIC_API' feature to be enabled.
Affected products
- Budibase Budibase < 3.39.0
Identifiers
- CVE-2026-48150
- GHSA-6xp4-cf37-ppjh
Timeline
- 2026-05-21: disclosed
- 2026-05-27: advisory: NVD publication
- 2026-06-12: patched: GitHub Advisory published/reviewed