CVE-2026-72850: Budibase before 3.40.0 Arbitrary File Write via Path Traversal
Budibase before 3.40.0 fails to properly sanitize S3 object keys, allowing authenticated builders to upload files with traversal sequences that are preserved during export. Attackers can craft filenames containing .. segments that escape the temporary directory during workspace export, writing arbitrary content to any path writable by the Budibase process.
Security readout for executives and security teams
Plain-English summary
Budibase versions before 3.40.0 allow an authenticated builder to manipulate uploaded filenames so workspace export writes attacker-controlled content outside its temporary directory. Files may be written anywhere the Budibase process has permission, creating serious integrity and availability risk.
Executive priority
Treat affected, reachable deployments as an urgent remediation item. Prioritize systems with numerous builder accounts, externally accessible authentication, broad filesystem permissions, or sensitive workloads. Investigate before upgrading if suspicious export or filesystem activity exists.
Technical view
Improper sanitization of S3 object keys preserves .. path segments through the export workflow. During workspace export, the resulting path can escape the intended temporary directory and cause an arbitrary file write. The issue is classified as CWE-22 and requires an authenticated, high-privilege builder account.
Likely exposure
Budibase server deployments running versions earlier than 3.40.0 are potentially exposed when untrusted or compromised builder accounts can upload content and trigger workspace exports. Actual impact depends on filesystem permissions granted to the Budibase process.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation nevertheless has low stated complexity after obtaining builder privileges and requires no user interaction.
Researcher notes
The attack crosses an S3 object-key trust boundary during export and becomes a local path traversal. Assessment should map upload, key persistence, export extraction, and destination-path handling. Evidence supplied supports arbitrary file write, but not a specific post-write execution path or confirmed exploitation.
Mitigation direction
Upgrade affected Budibase servers to version 3.40.0 or later.
Confirm remediation and deployment requirements against the vendor security advisory.
Restrict builder access to trusted users and remove unnecessary accounts.
Limit Budibase process write permissions to required application directories.
Temporarily restrict workspace exports where immediate upgrading is impossible.
Validation and detection
Inventory Budibase server versions and identify every instance earlier than 3.40.0.
Verify upgraded instances report version 3.40.0 or later.
Review builder accounts, authentication activity, uploads, and workspace exports for anomalies.
Search relevant records for filenames or object keys containing traversal segments.
Inspect process-writable locations for unexpected files associated with export activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.