← Back
CVE-2026-48128
SSRF (Server-Side Request Forgery) in budibase (CVE-2026-48128)
Summary
SSRF in budibase (CVE-2026-48128). Risk of unauthorized operations or information disclosure. Exploitable via ``inputs.query``. Mitigation: upgrade to `3.39.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48128** has been found in budibase.
Attackers can target a specific entry point like ``inputs.query`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade budibase to **3.39.0** or later.
If unsure, ask your IT team or search "budibase CVE-2026-48128" on the vendor's site.
CVE-2026-48128 (budibase) — CWE-918 /
Attack surface: `inputs.query` / `queryController.executeV2AsAutomation` / `context.user`
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
**SSRF** (CWE-918) exists in budibase. Attackers reach the vulnerable code path via ``inputs.query`` without authentication.
📍 Affected scope
budibase — . Attack surface: `inputs.query` / `queryController.executeV2AsAutomation` / `context.user`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 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 request patterns matching this CVE's known IOCs. Run `grep -r 'budibase' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'budibase' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `budibase` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade budibase to 3.39.0ステージング環境で 3.39.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
budibase
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.39.0"}]}]