Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-41428 — budibase

🔴 CVSS 9.5 — Critical ✅ No Known Exploit CWE-287 NVD
9.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Budibase: Authentication Bypass via Unanchored Regex in Public Endpoint Matcher — Unauthenticated Access to Protected Endpoints

Summary

The authenticated middleware uses unanchored regular expressions to match public (no-auth) endpoint patterns against ctx.request.url. Since ctx.request.url in Koa includes the query string, an attacker can access any protected endpoint by appending a public endpoint path as a query parameter. For example, POST /api/global/users/search?x=/api/system/status bypasses all authentication because the regex /api/system/status/ matches in the query string portion of the URL.

Details

Step 1 — Public endpoint patterns compiled without anchors

packages/backend-core/src/middleware/matchers.ts, line 26:

```typescript

return { regex: new RegExp(route), method, route }

```

No ^ prefix, no $ suffix. The regex matches anywhere in the test string.

Step 2 — Regex tested against full URL including query string

packages/backend-core/src/middleware/matchers.ts, line 32:

```typescript

const urlMatch = regex.test(ctx.request.url)

```

Koa's ctx.request.url returns the full URL including query string (e.g., /api/global/users/search?x=/api/system/status). The regex /api/system/status matches in the query string.

Step 3 — publicEndpoint flag set to true

packages/backend-core/src/middleware/authenticated.ts, lines 123-125:

```typescript

const found = matches(ctx, noAuthOptions)

if (found) {

publicEndpoint = true

}

```

Step 4 — Worker's global auth check skipped

packages/worker/src/api/index.ts, lines 160-162:

```typescript

.use((ctx, next) => {

if (ctx.publicEndpoint) {

return next() // ← SKIPS the auth check below

}

if ((!ctx.isAuthenticated || ...) && !ctx.internal) {

ctx.throw(403, "Unauthorized") // ← never reached

}

})

```

When ctx.publicEndpoint is true, the 403 check at line 165-168 is never executed.

Step 5 — Routes without per-route auth middleware are exposed

loggedInRoutes in packages/worker/src/api/routes/endpointGroups/standard.ts line 23:

```typescript

export const loggedInRoutes = endpointGroupList.group() // no middleware

```

Endpoints on loggedInRoutes have NO secondary auth check. The global check at index.ts:160-169 was their only protection.

Affected endpoints (no per-route auth — fully exposed):

  • POST /api/global/users/search — search all users (emails, names, roles)
  • GET /api/global/self — get current user info
  • GET /api/global/users/accountholder — account holder lookup
  • GET /api/global/template/definitions — template definitions
  • POST /api/global/license/refresh — refresh license
  • POST /api/global/event/publish — publish events

Not affected (have secondary per-route auth that blocks undefined user):

  • GET /api/global/users — on builderOrAdminRoutes which checks isAdmin(ctx.user) → returns false for undefined → throws 403
  • DELETE /api/global/users/:id — on adminRoutes → same secondary check blocks it

PoC

```bash

# Step 1: Confirm normal request is blocked

$ curl -s -o /dev/null -w "%{http_code}" \

-X POST -H "Content-Type: application/json" -d '{}' \

"https://budibase-instance/api/global/users/search"

403

# Step 2: Bypass auth via query string injection

$ curl -s -X POST -H "Content-Type: application/json" -d '{}' \

"https://budibase-instance/api/global/users/search?x=/api/system/status"

{"data":[{"email":"[email protected]","admin":{"global":true},...}],...}

```

Without auth → 403. With ?x=/api/system/status → returns all users.

Any public endpoint pattern works as the bypass value:

  • ?x=/api/system/status
  • ?x=/api/system/environment
  • ?x=/api/global/configs/public
  • ?x=/api/global/auth/default

Impact

An unauthenticated attacker can:

1. Enumerate all users — emails, names, roles, admin status, builder status via /api/global/users/search

2. Discover account holder — identify the instance owner via /api/global/users/accountholder

3. Trigger license refresh — potentially disrupt service via /api/global/license/refresh

4. Publish events — inject events into the event system via /api/global/event/publish

The user search is the most damaging — it reveals the full user directory of the Budibase instance to anyone on the internet.

Note: endpoints on builderOrAdminRoutes and adminRoutes are NOT affected because they have secondary middleware (workspaceBuilderOrAdmin, adminOnly) that independently checks ctx.user and throws 403 when it's undefined. Only loggedInRoutes endpoints (which rely solely on the global auth check) are exposed.

Suggested Fix

Two options (both should be applied):

Option A — Anchor the regex:

```typescript

// matchers.ts line 26

return { regex: new RegExp('^' + route + '(\\?|$)'), method, route }

```

Option B — Use ctx.request.path instead of ctx.request.url:

```typescript

// matchers.ts line 32

const urlMatch = regex.tes

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-41428 is classified as CWE-287: Improper Authentication. The identity of the caller is not established correctly, so an attacker can act as another user.

Affected software

CVE-2026-41428 is recorded against 2 packages.

  • @budibase/backend-core
  • budibase (fixed in 3.35.4)

Timeline and source

Published on 16 April 2026 and last revised on 5 May 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)

Other advisories for this package

@budibase/backend-core has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-287: Improper Authentication) in other software:

Details

Severity CRITICAL
CVSS Score 9.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CWE CWE-287
Public Exploit ✅ No
Source NVD
Published 2026-04-16
Updated 2026-08-20
Modified 2026-05-05
Fix URL N/A

Affected Packages

Software From version Fixed in
@budibase/backend-core
budibase 3.35.4

Similar Threats

Exploit Protection

Are you running budibase?

CVE-2026-41428 carries CVSS 9.5 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-41428 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026