Skip to main content
VulnerabilityPublished Updated

CVE-2026-72859: budibase server · Incorrect Authorization

Affects budibase serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 3.40.0 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.40.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade budibase server to 3.40.0.

Affected software

ProductAffectedFixed in
budibaseserverAffected
  • >=3.39.4 <3.40.0
Fixed in
  • 3.40.0
GitHubbudibase/budibasepkg:github/budibase/budibaseOther threatsAffected
  • =3.39.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Since Budibase server is a cloud service, the vendor manages remediation server-side. Users should verify with the vendor advisory that their service instance has been updated to version 3.40.0 or later where this issue is fixed. No additional mitigation actions are required if the patch is applied.

Description

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.

References

Community reviews

Loading reviews…