dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-46425

CRITICAL · 9.9 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 →
100/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.38.2, packages/worker/src/api/routes/global/scim.ts attaches only two middlewares to the SCIM router: requireSCIM (checks the Enterprise feature flag and SCIM config) and doInScimContext (sets the SCIM request context). There is no role check. Any authenticated user who reaches the worker (BASIC role, workspace-scoped builder, anyone) can call SCIM endpoints and CRUD every user and group in the tenant. This vulnerability is fixed in 3.38.2.

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 prior to 3.38.2, the SCIM router in packages/worker/src/api/routes/global/scim.ts only attaches two middlewares (requireSCIM and doInScimContext) that check Enterprise feature flags and set request context. No role-based authorization middleware exists, allowing any authenticated user—including those with BASIC role or workspace-scoped builder access—to access SCIM endpoints and perform CRUD operations on all users and groups within the tenant.

MitigationUpgrade Budibase to version 3.38.2 or later, which adds proper role-based authorization checks to the SCIM router middleware chain.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 by inspecting package.json, a version API endpoint, or the admin console. Compare against the fixed version 3.38.2.
    Affected if Version is lower than 3.38.2 and SCIM feature is enabled
  2. Locate the SCIM router file
    Inspect the file packages/worker/src/api/routes/global/scim.ts in the Budibase worker service installation. Examine the middleware chain applied to SCIM routes.
    Affected if The file only contains requireSCIM and doInScimContext middlewares without a role verification middleware
  3. Verify SCIM feature flag status
    Check the Budibase configuration or database settings for the SCIM feature flag (requireSCIM). This may be in environment variables, config tables, or the admin UI.
    Affected if SCIM feature is enabled (the requireSCIM check passes)
  4. Test SCIM endpoint accessibility
    Attempt to access SCIM endpoints (typically /api/global/scim/v2/) using credentials of a user with BASIC role or workspace-scoped builder permissions.
    Affected if Requests succeed without returning 403 Forbidden - indicating any authenticated user can access SCIM endpoints

A user is affected if they run Budibase version lower than 3.38.2, have SCIM enabled, and the scim.ts router lacks role-based access control middleware, allowing non-admin users to access SCIM endpoints.

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.38.2 or later, which adds proper role-based authorization checks to the SCIM router middleware chain.

Recommended fix High confidence

3.38.2

  1. 1. Identify the current Budibase version in use by checking the installed packages or the admin console.
  2. 2. Plan the upgrade to version 3.38.2, ensuring you have a backup of the current state.
  3. 3. Review the Budibase upgrade documentation for your deployment method (Docker, Kubernetes, or bare metal).
  4. 4. Execute the upgrade to Budibase version 3.38.2.
  5. 5. After upgrading, verify that the SCIM endpoints now properly enforce role-based authorization.
  6. 6. Test that regular users (BASIC role, workspace-scoped builders) can no longer access SCIM endpoints without proper SCIM-specific permissions.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46425 — 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-46425 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