All vulnerabilities

Servers and applications

CVE-2026-46425

SCIM endpoints lack role-based authorization, BASIC users CRUD tenant users

Severity
Critical 9.9
Published
14 May 2026
Last changed
14 May 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.38.2
Exploit chance
0.3% in the next 30 daysHigher than 21% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Missing authorization (CWE-862)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read data · Change data · Take it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Also known as
GHSA-q9rw-q89f-jx2f
Sources
Project advisories (GitHub)

Description

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. The non-SCIM equivalents at /api/global/groups already enforce auth.adminOnly; the SCIM routes are the missing half of that pair.

SCIM router as currently wired:

requireSCIM (packages/pro/src/middleware/requireSCIM.ts:5-9) calls features.checkSCIM(), which confirms the SCIM feature is licensed and the tenant has enabled SCIM. It does not look at the caller's role.

Compare the non-SCIM group router:

auth.adminOnly and auth.builderOrAdmin are present on every user- and group-mutating route. The SCIM twin of each has neither.

From Budibase/budibase's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
BudibaseServers and applications · github:budibase/budibase
  • Every version before 3.38.2

About Budibase

low-code development platform

From Wikidata, CC0 1.0.
Docker Hub pulls
2,327,272Docker Hub, 15 Nov 2026
GitHub stars
28,419GitHub, 15 Nov 2026
Forks
2,238GitHub, 15 Nov 2026
Latest release
v4.0.0GitHub, 15 Nov 2026
Released
10 Nov 2026GitHub
First published on GitHub
7 Jun 2019GitHub

References