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.
Original description
The description as published by the source.
Budibase is an open-source low-code platform. Prior to 3.39.0, the executeQuery automation step in Budibase accepts a queryId from automation step inputs and passes it directly to the query execution controller without additional validation. When combined with a REST datasource configured to target internal infrastructure, this creates a server-side request forgery path where automation execution causes the Budibase server to make outbound HTTP requests to attacker-influenced destinations. The automation output then returns the response, potentially exposing internal service data. 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-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.
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.
SSRF (CWE-918) exists in budibase. Attackers reach the vulnerable code path via inputs.query.
Check the vendor advisory for the affected versions of budibase. Attack surface: inputs.query / queryController.executeV2AsAutomation / context.user.
Severity: ?. Risk of unauthorized operations or information disclosure.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
budibaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade budibase 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