SSRF (Server-Side Request Forgery) in @budibase/server (CVE-2026-48153)
Summary
SSRF in @budibase/server (CVE-2026-48153). Confidential information can be exposed externally. Exploitable via fetchToken. 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, fetchToken in the OAuth2 SDK makes a POST to a builder-supplied URL with plain node-fetch, skipping the blacklist.isBlacklisted check that every other outbound fetch path in the codebase uses. The Joi schema for the OAuth2 URL has no scheme or host restriction. 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-48153 has been found in @budibase/server.
Attackers can target a specific entry point like fetchToken over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/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-48153" on the vendor's site.
CVE-2026-48153 (@budibase/server) — CWE-918 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: fetchToken / blacklist.isBlacklisted / config.url / fetchConfig
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.
SSRF (CWE-918) exists in @budibase/server. Attackers reach the vulnerable code path via fetchToken.
Check the vendor advisory for the affected versions of @budibase/server. Attack surface: fetchToken / blacklist.isBlacklisted / config.url / fetchConfig.
Severity: High (CVSS 8.5/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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @budibase/server to 3.39.0ステージング環境で 3.39.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com