Path Traversal in @budibase/server (CVE-2026-54352)
Summary
Path traversal in @budibase/server (CVE-2026-54352). Confidential information can be exposed externally. Exploitable via POST /api/pwa/process-zip. Mitigation: upgrade to 3.39.9 or later.
Original description
The description as published by the source.
Budibase is an open-source low-code platform. Prior to 3.39.9, POST /api/pwa/process-zip at packages/server/src/api/routes/static.ts:24 accepts a builder-uploaded .zip, extracts it with extract-zip@2.0.1 into a temp directory, then for each entry listed in icons.json validates the icon path, opens it, and streams the bytes into MinIO. The resulting object is served back via GET /api/assets/{appId}/pwa/{uuid}.png. extract-zip@2.0.1 preserves absolute symlink targets when restoring symlink entries. The icon-source validator at packages/server/src/api/controllers/static/index.ts:259-268 resolves the icon source string against baseDir (path.resolve), checks resolvedSrc.startsWith(baseDir + path.sep) against that string, and calls fs.existsSync(resolvedSrc) which follows symbolic links to confirm the target exists. None of the three calls reject symbolic-link entries. packages/backend-core/src/objectStore/objectStore.ts:302 then calls (await fsp.open(path)).createReadStream() on the resolved path. fsp.open follows the symlink, the target file's bytes stream into MinIO, and the response of the asset-fetch endpoint returns those bytes verbatim. Result: a workspace-level builder reads any file the server process can open. This vulnerability is fixed in 3.39.9.
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-54352 has been found in @budibase/server.
Attackers can target a specific entry point like POST /api/pwa/process-zip over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade @budibase/server to 3.39.9 or later.
If unsure, ask your IT team or search "@budibase/server CVE-2026-54352" on the vendor's site.
CVE-2026-54352 (@budibase/server) — CWE-22 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/pwa/process-zip / GET /api/assets/{appId}/pwa/{uuid}.png / GET /api/assets/{appId}/pwa/{uuid}.{ext} / GET /api/global/self
Patched: 3.39.9 — 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.
Path traversal (CWE-22) exists in @budibase/server. Attackers reach the vulnerable code path via POST /api/pwa/process-zip.
Check the vendor advisory for the affected versions of @budibase/server. Attack surface: POST /api/pwa/process-zip / GET /api/assets/{appId}/pwa/{uuid}.png / GET /api/assets/{appId}/pwa/{uuid}.{ext} / GET /api/global/self.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 3.39.9.
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/pwa/process-zip requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/pwa/process-zip' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/pwa/process-zipへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @budibase/server to 3.39.9ステージング環境で 3.39.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/pwa/process-zip 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