Loading vulnerability…
CVE-2026-54356 is an improper authorization vulnerability in Budibase before version 3.41.3. The server-side attachment signed-upload URL issuance flow validates TABLE write permission instead of requiring DATASOURCE write permission. Consequently, an authenticated published-application user assigned the BASIC role can submit attacker-controlled S3 bucket and object-key parameters and receive signed and public URLs generated with the backend S3 datasource credentials. The flaw enables use of credential-authorized S3 storage locations beyond those intended for the requesting user.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a concise PoC for CVE-2026-54356 affecting Budibase/@budibase/server before 3.41.3. Structure is minimal: a README describing the vulnerability and impact, plus two exploit implementations under poc/: a Bash/curl script and a Python requests-based script. Both follow the same three-step flow: authenticate to a published Budibase app as a low-privilege BASIC user via /api/global/auth/<app_id>/login, call the vulnerable endpoint /api/attachments/<datasourceId>/url with attacker-controlled bucket and key values, then optionally use the returned S3 pre-signed URL to upload proof content with HTTP PUT. The exploit demonstrates an authorization flaw, not code execution: Budibase improperly allows a BASIC user with generic table-write permission to mint S3 PutObject signed URLs using server-side AWS credentials tied to a datasource, without verifying authorization for that datasource. Main capability is unauthorized issuance of usable S3 upload URLs and consequent arbitrary object write/overwrite within the permissions of the datasource credentials. The Bash script is a minimal operational PoC using curl and sed to extract signedUrl; the Python script is more robust, supports CLI arguments, optional TLS verification disablement, and optional proof upload. No destructive or fake behavior is present.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authenticated authorization flaw in Budibase's attachment URL endpoint permits BASIC-role users of published applications, when they know a valid datasource ID, to mint AWS S3 PUT pre-signed URLs using server-side datasource credentials and attacker-controlled bucket and object-key values.
An authenticated, low-privilege authorization flaw in Budibase that permits arbitrary issuance of S3 pre-signed upload URLs using the backend server's AWS credentials. An attacker can modify, overwrite, delete, or upload objects in accessible S3 buckets, potentially causing stored XSS when static web assets are overwritten, resource exhaustion, and cloud-cost impact.
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.