Budibase: Missing RBAC on GET /api/global/groups allows BASIC users to enumerate all tenant groups and role mappings
CVE-2026-73301GHSA-4qcj-m5wp-jmf4
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @budibase/server
- Affected
- <= 3.38.1
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4qcj-m5wp-jmf4 lists affected ranges: npm @budibase/server >=0 <=3.38.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4qcj-m5wp-jmf4 lists affected ranges: npm @budibase/server >=0 <=3.38.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-73301: 0.34% estimated exploitation activity in the next 30 days; percentile 27.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The GET /api/global/groups endpoint on the worker service has no role-based authorization middleware. Any authenticated user (including BASIC role) can enumerate all user groups in the tenant, including their role mappings, user memberships, builder permissions, and the isDefault flag. Steps to Reproduce 1. Start Budibase 2. Login as admin, create a user group, create a BASIC user 3. Login as BASIC user and enumerate all groups (the vulnerability) Expected: 403 Forbidden (consistent with GET /api/global/groups/:id which requires builderOrAdmin) Actual: 200 OK with full group data including role mappings, member lists, and builder flags. Standalone verification (code review) Output shows the list endpoint has NO auth middleware: Compare with the single-group endpoint directly below: Root Cause File: packages/worker/src/api/routes/global/groups.ts, lines 40-44 The list endpoint is the ONLY group endpoint without RBAC: | Endpoint | Auth Middleware | |----------|---------------|…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-4qcj-m5wp-jmf4
- Revision 1 · created ·
Published from osv record GHSA-4qcj-m5wp-jmf4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-73301 Advisory: Budibase: Missing RBAC on GET /api/global/groups allows BASIC users to enumerate all tenant groups and role mappings IDs: CVE-2026-73301, GHSA-4qcj-m5wp-jmf4 Record: https://patchnext.com/advisories/cve-2026-73301 (revision 2, source checked 26 Oct 2026, 13:01 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @budibase/server: affected <= 3.38.1 ## Suggested inspection (read-only) - `npm ls @budibase/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @budibase/server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-4qcj-m5wp-jmf4 (OSV record GHSA-4qcj-m5wp-jmf4 lists affected ranges: npm @budibase/server >=0 <=3.38.1) - Verified: https://github.com/advisories/GHSA-4qcj-m5wp-jmf4 (GitHub-reviewed advisory GHSA-4qcj-m5wp-jmf4 lists affected ranges: npm @budibase/server >=0 <=3.38.1) Commands are suggestions: review each one before running it.
Loading voting…