Privilege Escalation in @budibase/backend-core (CVE-2026-46424)
Summary
Vulnerability in @budibase/backend-core (CVE-2026-46424). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/public/v1/roles/unassign. 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, the public API role unassignment endpoint (POST /api/public/v1/roles/unassign) updates user documents in CouchDB but does not invalidate the corresponding Redis user cache entries. Because the authentication middleware resolves user identity and permissions from this cache (TTL: 3600 seconds), a user whose admin, builder, or app-level roles have been revoked via the public API retains those privileges for up to 1 hour. This vulnerability is fixed in 3.38.2.
Source: GitHub Security Advisories (Global) 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-46424 has been found in @budibase/backend-core.
Attackers can target a specific entry point like POST /api/public/v1/roles/unassign over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade @budibase/backend-core to 3.38.2 or later.
If unsure, ask your IT team or search "@budibase/backend-core CVE-2026-46424" on the vendor's site.
CVE-2026-46424 (@budibase/backend-core) — CWE-269 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/public/v1/roles/unassign / bulkUpdate / unAssign / assign
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-269) exists in @budibase/backend-core. Attackers reach the vulnerable code path via POST /api/public/v1/roles/unassign.
Check the vendor advisory for the affected versions of @budibase/backend-core. Attack surface: POST /api/public/v1/roles/unassign / bulkUpdate / unAssign / assign.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
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 POST /api/public/v1/roles/unassign requests with malformed payloads or SQL meta-characters. Run grep -r '@budibase/backend-core' . 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/backend-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@budibase/backend-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/public/v1/roles/unassign' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/public/v1/roles/unassignへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @budibase/backend-core to 3.38.2ステージング環境で 3.38.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/public/v1/roles/unassign 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
- web github.com