Budibase arbitrary file read via PWA ZIP symlink upload
CVE-2026-54352 is an arbitrary file-read vulnerability in Budibase prior to version 3.39.9. The issue exists in the PWA ZIP processing workflow exposed through POST /api/pwa/process-zip (packages/server/src/api/routes/static.ts:24). A workspace-level builder can upload a crafted ZIP archive containing symlink entries and an icons.json that references those entries. Budibase extracts the archive using extract-zip@2.0.1, which preserves absolute symlink targets. During validation in packages/server/src/api/controllers/static/index.ts:259-268, the application resolves the icon path against baseDir, checks that the resolved string begins with baseDir + path.sep, and calls fs.existsSync(resolvedSrc). However, these checks do not reject symlink entries, and fs.existsSync follows symlinks. Later, packages/backend-core/src/objectStore/objectStore.ts:302 opens the resolved path with (await fsp.open(path)).createReadStream(), which also follows the symlink. As a result, the server reads the symlink target and streams its contents into MinIO, after which the bytes are retrievable via GET /api/assets/{appId}/pwa/{uuid}.png. This allows a builder to read any file the server process can access.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
POST /api/pwa/process-zip functionality for workspace builders, reject symlink entries during ZIP extraction and post-extraction validation, sanitize uploaded archives before processing, and disable symlink following where feasible. Additionally, run the Budibase server with least privilege, avoid running as root, and isolate sensitive files and secrets from the application filesystem to reduce exposure.Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.