Authorization Flaw in @budibase/server (CVE-2026-48152)
Summary
Vulnerability in @budibase/server (CVE-2026-48152). Confidential information can be exposed externally. Exploitable via GET /api/datasources/. 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, the single-datasource GET and PUT routes are guarded by generic TABLE READ, not by Builder/Admin permission or datasource-specific ownership/resource checks. The built-in Basic app user role maps to the WRITE permission set, which includes table read/write and query write. A Basic user can therefore read an existing REST datasource, receive redacted authConfigs values, submit an update that changes only config.url while keeping the redacted placeholders, and trigger an existing saved relative-path REST query. During update, mergeConfigs() restores the old stored secret when it sees the redaction placeholder. During query execution, Budibase prefixes the attacker-controlled datasource config.url to the relative query path and applies the resolved stored auth headers. The result is server-side disclosure of the builder-configured REST Authorization secret to an attacker-controlled listener. 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-48152 has been found in @budibase/server.
Attackers can target a specific entry point like GET /api/datasources/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/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-48152" on the vendor's site.
CVE-2026-48152 (@budibase/server) — CWE-863 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/datasources/ / PUT /api/datasources/ / POST /api/v2/queries/ / GET /api/datasources/{datasourceId}
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.
Incorrect authorization (CWE-863) exists in @budibase/server. Attackers reach the vulnerable code path via GET /api/datasources/.
Check the vendor advisory for the affected versions of @budibase/server. Attack surface: GET /api/datasources/ / PUT /api/datasources/ / POST /api/v2/queries/ / GET /api/datasources/{datasourceId}.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 3.39.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/datasources/ 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
-
1Identify exposure identify
grep -r '@budibase/server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@budibase/serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/datasources/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/datasources/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @budibase/server to 3.39.0ステージング環境で 3.39.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/datasources/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com