EUVD-2026-57430
GHSA-hfhx-w8p8-4hc7
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Builder-level auth required (PR:L); scope changes as server reaches subsequent internal systems (S:C); high confidentiality loss via cloud metadata exposure (C:H); no integrity or availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
Budibase is an open-source low-code platform. Prior to 3.39.4, uploadUrl in packages/server/src/utilities/fileUtils.ts used a bare server-side fetch for string attachment values passed by processAttachments in packages/server/src/sdk/workspace/ai/helpers/rows.ts. A builder with the AI table-generation feature could cause an attachment value to reference an internal service or cloud metadata endpoint, and the response would be stored as an attachment without fetchWithBlacklist validation. This issue is fixed in version 3.39.4.
AnalysisAI
Server-Side Request Forgery in Budibase's AI table generation pipeline (versions prior to 3.39.4) allows a builder-level user to coerce the server into fetching arbitrary internal network endpoints - including cloud metadata services such as 169.254.169.254 - by crafting LLM prompts that cause the AI to output internal IP addresses as attachment column values. The vulnerable code path, uploadUrl() in fileUtils.ts, uses a bare node-fetch call with no SSRF blacklist validation, while sibling code paths in the same codebase correctly use fetchWithBlacklist(). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must hold a builder-level (or higher) account within the target Budibase instance - viewer and standard app-user roles cannot invoke the AI table generation workflow (`generateRows()`). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-assigned CVSS 4.0 score of 4.9 (AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N) reflects a nuanced picture: the vulnerable system itself suffers no direct confidentiality, integrity, or availability impact (VC/VI/VA all N), but the subsequent-system confidentiality impact is rated High (SC:H), capturing the real risk - server-side fetching of cloud metadata endpoints can expose IAM credentials on AWS IMDSv1 deployments, enabling privilege escalation well beyond the Budibase application boundary. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A builder-level user with access to an AI-configured Budibase instance creates a new table using the AI table generation feature, crafting the LLM prompt to describe an attachment column that should reference a specific URL. By shaping the prompt to elicit internal endpoints such as `http://169.254.169.254/latest/meta-data/iam/security-credentials/`, the builder causes `generateRows()` to pass that URL string into `processAttachments()`, which calls `uploadUrl()` to fetch it server-side via bare `fetch()` without blacklist validation. … |
| Remediation | The primary fix is upgrading Budibase to version 3.39.4 or later, available at https://github.com/Budibase/budibase/releases/tag/3.39.4. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Unauthorized data access in Budibase low-code platform before 3.30.4 allows unauthenticated users to manipulate internal
Authorization bypass in Budibase 3.31.4 and earlier. The authorized() middleware can be bypassed, enabling injection att
Budibase is a low code platform for creating internal tools, workflows, and admin panels. [CVSS 8.8 HIGH]
Unauthenticated user enumeration and metadata disclosure in Budibase prior to 3.39.32 exposes tenant identifiers, email
Server-Side Request Forgery (SSRF) in Budibase's REST datasource connector (versions prior to 3.33.4) allows authenticat
OAuth2 access and refresh token theft in Budibase's automation testing pipeline exposes SSO-authenticated builder creden
Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20. Rated med
Path traversal in Budibase low-code platform 3.31.5 and earlier allows attackers to read arbitrary files through the app
SQL injection in Budibase's MySQL integration (all versions prior to 3.40.0) lets attackers execute arbitrary, stacked S
Account enumeration and targeted denial-of-service in Budibase prior to 3.39.25 stem from an observable response discrep
Filesystem existence and readability probing in Budibase Cloud's MongoDB integration prior to version 3.40.1 exposes an
Authentication bypass in Budibase low-code platform (versions prior to 3.35.4) allows remote unauthenticated attackers t
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today