Categories
CVE-2026-48150 critical CVSS 9.0

Vulnerability in @budibase/server (CVE-2026-48150)

Summary

Vulnerability in @budibase/server (CVE-2026-48150). Confidential information can be exposed externally. Exploitable via GET /api/global/self/api_key. Mitigation: upgrade to 3.39.0 or later.

Original description

The description as published by the source.

Budibase is an open-source low-code platform. Prior to 3.39.0, /api/public/v1/roles/assign is guarded by the builderOrAdmin middleware, which passes any user who is a builder for the app id in the x-budibase-app-id header. That check admits both global builders and workspace-scoped builders (builder.apps set but builder.global unset). The controller then spreads the request body into the SDK call, and the SDK grants builder.global=true or admin.global=true on whichever user ids the caller supplies. Bob, a workspace-scoped builder with an API key, promotes himself or any other user to global admin with one POST. The whole flow is tenant-wide privilege escalation from an app-level role, available to anyone with an Enterprise license that unlocks the EXPANDED_PUBLIC_API feature. This vulnerability is fixed in 3.39.0.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48150 has been found in @budibase/server.
Attackers can target a specific entry point like GET /api/global/self/api_key over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.0/10.
What to do: upgrade @budibase/server to 3.39.0 or later.
If unsure, ask your IT team or search "@budibase/server CVE-2026-48150" on the vendor's site.

CVE-2026-48150 (@budibase/server) — CWE-915 / CVSS v3 9.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/global/self/api_key / builderOrAdmin / builder.apps / builder.global
Patched: 3.39.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-915) exists in @budibase/server. Attackers reach the vulnerable code path via GET /api/global/self/api_key.

📍 Affected scope

Check the vendor advisory for the affected versions of @budibase/server. Attack surface: GET /api/global/self/api_key / builderOrAdmin / builder.apps / builder.global.

🔥 Severity

Severity: Critical (CVSS 9.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.39.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/global/self/api_key requests with malformed payloads or SQL meta-characters. Run grep -r '@budibase/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@budibase/server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @budibase/server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /api/global/self/api_key' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/global/self/api_key への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade @budibase/server to 3.39.0

    ステージング環境で 3.39.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /api/global/self/api_key on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @budibase/server
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.39.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details