CVE-2026-50136: Budibase Remote Code Execution Vulnerability
HIGHCVE-2026-50136 is a HIGH (CVSS 7.4) remote code execution vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Budibase libraries in the npm ecosystem. The issue involves unauthenticated s3 signed upload url generation allows arbitrary writes with stored datasource credentials. Remediation is available by upgrading affected packages to version 3.39.2.
CVE-2026-50136 at a Glance
Security Impact
CVSS: 7.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L).
How to Fix CVE-2026-50136
To remediate this vulnerability, upgrade all affected Budibase dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @budibase/server@3.39.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @budibase/server
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-50136, inspect your project dependencies using npm:
npm ls @budibase/server
Analyze the terminal output to locate any version of Budibase in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.39.2), your application is affected.
Note: The npm ls @budibase/server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Budibase, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-50136 Affected Budibase Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@budibase/server
|
npm |
< 3.39.2
|
3.39.2
|
References
Frequently Asked Questions
What is CVE-2026-50136?
Which Budibase versions are affected?
What version fixes CVE-2026-50136?
Is @budibase/server affected?
What is the CVSS score of CVE-2026-50136?
What CWE is associated with CVE-2026-50136?
How can I check npm dependencies for CVE-2026-50136?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jj36-r9w3-3pfh",
"modified" : "2026-07-17T16:59:09Z",
"published" : "2026-06-22T23:15:10Z",
"aliases" : [ "CVE-2026-50136" ],
"summary" : "Budibase: Unauthenticated S3 signed upload URL generation allows arbitrary writes with stored datasource credentials",
"details" : "The application server exposes an unauthenticated endpoint that generates S3 `PutObject` presigned URLs using credentials stored in a workspace datasource. The route is protected only by the recaptcha middleware and does not require authentication, table permission, datasource permission, or builder access. A public caller who knows a workspace ID and S3 datasource ID can request a signed upload URL for attacker-controlled bucket and key values.\n\n### Details\n\nThe static route registers the signed upload URL endpoint with only `recaptcha` before the controller:\n\n- `packages/server/src/api/routes/static.ts:44-48`\n\n```ts\n44: .post(\n45: \"/api/attachments/:datasourceId/url\",\n46: recaptcha,\n47: controller.getSignedUploadURL\n48: )\n```\n\nThe controller loads the datasource by `datasourceId` with enriched secret values:\n\n- `packages/server/src/api/controllers/static/index.ts:590-598`\n\n```ts\n590:export const getSignedUploadURL = async function (\n591: ctx: Ctx<GetSignedUploadUrlRequest, GetSignedUploadUrlResponse>\n592:) {\n593: // Ensure datasource is valid\n594: let datasource\n595: try {\n596: const { datasourceId } = ctx.params\n597: datasource = await sdk.datasources.get(datasourceId, { enriched: true })\n598: if (!datasource) {\n```\n\nThe request body controls `bucket` and `key`, and the server signs a PUT URL using the stored datasource credentials:\n\n- `packages/server/src/api/controllers/static/index.ts:609-629`\n\n```ts\n609: if (datasource?.source === \"S3\") {\n610: const { bucket, key } = ctx.request.body || {}\n611: if (!bucket || !key) {\n612: ctx.throw(400, \"bucket and key values are required\")\n613: }\n614: try {\n615: let endpoint = datasource?.config?.endpoint\n616: if (endpoint && !utils.urlHasProtocol(endpoint)) {\n617: endpoint = `https://${endpoint}`\n618: }\n619: const s3 = new S3({\n620: region: awsRegion,\n621: endpoint: endpoint,\n622: credentials: {\n623: accessKeyId: datasource?.config?.accessKeyId as string,\n624: secretAccessKey: datasource?.config?.secretAccessKey as string,\n625: },\n626: })\n627: const params = { Bucket: bucket, Key: key }\n628: signedUrl = await getSignedUrl(s3, new PutObjectCommand(params))\n629: if (endpoint) {\n```\n\nThe endpoint returns the signed URL and public URL to the caller:\n\n- `packages/server/src/api/controllers/static/index.ts:630-639`\n\n```ts\n630: publicUrl = `${endpoint}/${bucket}/${key}`\n631: } else {\n632: publicUrl = `https://${bucket}.s3.${awsRegion}.amazonaws.com/${key}`\n633: }\n634: } catch (error: any) {\n635: ctx.throw(400, error)\n636: }\n637: }\n638:\n639: ctx.body = { signedUrl, publicUrl }\n```\n\nBecause no authorization middleware is applied, the API trusts public input to choose where the stored S3 credentials will write.\n\n### PoC\n\nNon-destructive validation approach:\n\n1. Create or identify a workspace with an S3 datasource.\n2. Obtain the production workspace ID and S3 datasource ID.\n3. Send an unauthenticated request with the workspace ID header and attacker-controlled bucket/key:\n\n```http\nPOST /api/attachments/<datasourceId>/url HTTP/1.1\nx-budibase-app-id: app_<workspace-id>\ncontent-type: application/json\n\n{\"bucket\":\"attacker-controlled-or-permitted-bucket\",\"key\":\"poc/budibase.txt\"}\n```\n\n4. Observe that the response contains a signed PUT URL.\n5. Upload harmless content to the returned `signedUrl` and confirm the object is created using the datasource's stored S3 credentials.\n\n### Impact\n\nThis allows unauthenticated arbitrary object writes wherever the stored S3 datasource credentials have `PutObject` access. Depending on the datasource permissions, this can corrupt application data, overwrite public assets, place attacker-controlled objects in trusted buckets, consume storage, or abuse an organization's cloud credentials.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@budibase/server"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.39.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Budibase/budibase/security/advisories/GHSA-jj36-r9w3-3pfh"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-50136"
}, {
"type" : "WEB",
"url" : "https://github.com/Budibase/budibase/pull/18774"
}, {
"type" : "WEB",
"url" : "https://github.com/Budibase/budibase/commit/d9dbb7f6105373cc88ecacdbcab70c776f7dd6a1"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Budibase/budibase"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-306" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-22T23:15:10Z",
"nvd_published_at" : "2026-06-26T21:16:34Z"
}
}