Vulnerability in Budibase (CVE-2026-46425)
Summary
Vulnerability in Budibase (CVE-2026-46425). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.38.2 or later.
Original description
The description as published by the source.
Budibase is an open-source low-code platform. Prior to 3.38.2, packages/worker/src/api/routes/global/scim.ts attaches only two middlewares to the SCIM router: requireSCIM (checks the Enterprise feature flag and SCIM config) and doInScimContext (sets the SCIM request context). There is no role check. Any authenticated user who reaches the worker (BASIC role, workspace-scoped builder, anyone) can call SCIM endpoints and CRUD every user and group in the tenant. This vulnerability is fixed in 3.38.2.
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-46425 has been found in Budibase.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade Budibase to 3.38.2 or later.
If unsure, ask your IT team or search "Budibase CVE-2026-46425" on the vendor's site.
CVE-2026-46425 (Budibase) — CWE-862 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.38.2 — 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.
A vulnerability (CWE-862) exists in Budibase.
Check the vendor advisory for the affected versions of Budibase.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 3.38.2.
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.38.2ステージング環境で 3.38.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com