Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:HSummary
CVE-2026-35214 is a high-severity Path Traversal (CWE-22) vulnerability in Budibase Budibase. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-35214 is a path traversal vulnerability (CWE-22) in Budibase, an open-source low-code platform. In versions prior to 3.33.4, the plugin file upload endpoint (POST /api/plugin/upload) passes user-supplied filenames directly to the createTempFolder() function without sanitizing path traversal sequences like ../. This flaw has a CVSS v3.1 base score of 8.7 (AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H).
An authenticated attacker with Global Builder privileges can exploit the vulnerability over the network with low complexity and no user interaction. By crafting a multipart upload request with a filename containing ../ sequences, the attacker can delete arbitrary directories via rmSync and write arbitrary files via tarball extraction to any filesystem path accessible by the Node.js process, potentially leading to significant integrity and availability impacts across the scoped components.
The vulnerability has been patched in Budibase version 3.33.4. Mitigation involves upgrading to this version or later. Official resources include the patching commit (https://github.com/Budibase/budibase/commit/6344d06d703660fd05995e61d581593c2349c879), pull request (https://github.com/Budibase/budibase/pull/18240), release tag (https://github.com/Budibase/budibase/releases/tag/3.33.4), and security advisory (https://github.com/Budibase/budibase/security/advisories/GHSA-2wfh-rcwf-wh23).
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18793
Vulnerability Data
Budibase is an open-source low-code platform. Prior to version 3.33.4, the plugin file upload endpoint (POST /api/plugin/upload) passes the user-supplied filename directly to createTempFolder() without sanitizing path traversal sequences. An attacker with Global Builder privileges can craft a multipart upload…
more
with a filename containing ../ to delete arbitrary directories via rmSync and write arbitrary files via tarball extraction to any filesystem path the Node.js process can access. This issue has been patched in version 3.33.4.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.