PatchSiren cyber security CVE debrief
CVE-2026-72859 budibase CVE debrief
Budibase versions 3.39.4 before 3.40.0 contain an authorization regression in the S3 attachment upload endpoint that allows BASIC users to obtain S3 PutObject presigned URLs by sending POST requests to the attachments endpoint. The route was changed from a BUILDER permission check to a TABLE/WRITE check, which BASIC users hold by default. Attackers can specify arbitrary S3 buckets in the request body to generate presigned URLs for writing to any bucket accessible by the stored IAM credentials, enabling unauthorized file uploads. Evidence is limited; verify affected versions and patch status. Budibase users should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Vendor
- budibase
- Product
- server
- CVSS
- HIGH 8.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-14
- Original CVE updated
- 2026-08-31
- Advisory published
- 2026-08-14
- Advisory updated
- 2026-08-31
Who should care
Budibase users, administrators, and security teams should be aware of this vulnerability and take steps to patch or mitigate. Budibase users should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented. Budibase users should prioritize patching to prevent unauthorized file uploads and review compensating controls for exposed systems while remediation is scheduled and verified.
Technical summary
Budibase versions 3.39.4 before 3.40.0 contain an authorization regression in the S3 attachment upload endpoint. BASIC users can obtain S3 PutObject presigned URLs by sending POST requests to the attachments endpoint, allowing unauthorized file uploads to any bucket accessible by the stored IAM credentials. This vulnerability enables attackers to specify arbitrary S3 buckets in the request body to generate presigned URLs for writing to any bucket. Budibase users should prioritize patching to prevent unauthorized file uploads and review compensating controls for exposed systems while remediation is scheduled and verified.
Defensive priority
Budibase users should prioritize patching to prevent unauthorized file uploads.
Recommended defensive actions
- Patch Budibase to version 3.40.0 or later
- Restrict access to S3 buckets
- Monitor for unauthorized file uploads
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
Evidence notes
Budibase versions 3.39.4 before 3.40.0 contain an authorization regression in the S3 attachment upload endpoint that allows BASIC users to obtain S3 PutObject presigned URLs by sending POST requests to the attachments endpoint. The route was changed from a BUILDER permission check to a TABLE/WRITE check, which BASIC users hold by default. Attackers can specify arbitrary S3 buckets in the request body to generate presigned URLs for writing to any bucket accessible by the stored IAM credentials, enabling unauthorized file uploads. Evidence is limited; verify affected versions and patch status. Budibase users should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72859 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72859
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72859 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72859
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Budibase/budibase/security/advisories/GHSA-xcx6-4f2g-hhgx
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/budibase-before-authorization-regression-via-s3-presigned-url
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.