Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Builder-role credentials
-
DeliverySubmit crafted POST /api/queries/preview to 100.64.0.0/10 target
-
ExploitBypass incomplete DEFAULT_BLACKLIST (missing range)
-
ExecutionBudibase server forwards HTTP request to internal target
-
PersistInternal service response proxied back via preview API
-
ImpactAttacker reads confidential internal service data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an account with the Builder permission on a self-hosted Budibase instance - Builder is a named privilege tier that grants access to datasource query preview functionality. The deployment must be relying on the DEFAULT_BLACKLIST, meaning the BLACKLIST_IPS environment variable has not been defined (defining it with any value replaces DEFAULT_BLACKLIST). A reachable HTTP or HTTPS service must exist within 100.64.0.0/10 from the Budibase server's network perspective - this depends entirely on the hosting environment, making the vulnerability inert in networks where 100.64.0.0/10 is not routed internally. Exploitation is limited by: (1) required Builder-role authentication, ruling out anonymous or Viewer-only users; (2) self-hosted deployment context with no BLACKLIST_IPS override; (3) environment-specific presence of a target service on 100.64.0.0/10. Cloud-managed Budibase.com is not referenced as affected. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N) scores 7.1, reflecting a network-accessible, low-complexity exploit requiring only Builder-level privileges with no user interaction, and high confidentiality impact from exposed internal service data. Real-world risk is significantly gated by deployment context: the vulnerability applies only to self-hosted Budibase instances that have not defined BLACKLIST_IPS, and only in network environments where 100.64.0.0/10 addresses front reachable internal services (CGNAT, specific cloud configurations). Organizations whose Budibase server cannot route to 100.64.0.0/10 are not materially exposed. EPSS data is not available in the provided intelligence. No KEV listing exists and no public POC has been identified, suggesting this has not been broadly weaponized. The primary risk profile is insider threat or compromised Builder-role credential scenarios in sensitive self-hosted environments. The high VC score is appropriate for environments where 100.64.0.0/10 services expose credentials, configuration, or metadata - but this is infrastructure-dependent. |
| Exploit ScenarioDerived | An authenticated Budibase Builder submits a REST datasource query preview via POST /api/queries/preview with a target URL pointing to an HTTP service within 100.64.0.0/10 - for example, a cloud provider's internal management API or a CGNAT-routed microservice reachable from the Budibase host. The server processes the request through the incomplete DEFAULT_BLACKLIST, forwards it to the target, and returns the full HTTP response body to the Builder through the standard preview response, exposing internal service content such as configuration data, credentials, or tokens. No public proof-of-concept code has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Server-Side Request Forgery in Budibase Server self-hosted deployments exposes internal services on the RFC 6598 shared address space (100.64.0.0/10) by omitting that range from the default SSRF blacklist (DEFAULT_BLACKLIST) used for REST datasource query preview requests. Authenticated users holding the Builder role can submit a crafted POST /api/queries/preview request targeting a reachable host in 100.64.0.0/10, causing the Budibase server to proxy the request and return the internal service response through the preview flow, potentially exposing confidential internal data. No released patch has been identified; exploitation requires Builder-role access and a self-hosted deployment without a custom BLACKLIST_IPS override. No public exploit or CISA KEV listing has been identified at time of analysis.
RemediationAI
No released patch has been identified at the time of this analysis - the advisory explicitly states that remediation is via configuration override rather than a code fix. The primary workaround is to define the BLACKLIST_IPS environment variable on the self-hosted Budibase server to include 100.64.0.0/10 along with all other private, reserved, and sensitive address ranges: RFC 1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback (127.0.0.0/8), link-local (169.254.0.0/16, including cloud metadata service IPs such as 169.254.169.254), and IPv6 equivalents as appropriate. Note that defining BLACKLIST_IPS replaces, rather than extends, the DEFAULT_BLACKLIST, so all desired blocked ranges must be enumerated explicitly - omitting other private ranges when setting this variable would introduce new exposure. As a defense-in-depth measure, restrict the Builder role to fully trusted users, since this privilege is a hard requirement for exploitation. Monitor the vendor advisory at https://github.com/Budibase/budibase/security/advisories/GHSA-9754-4wm6-3c8r for a patched release.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Budibase is an open-source low-code application platform. Its backend-core package (@budibase/backend-core) implements SSRF protection for the REST datasource feature via a DEFAULT_BLACKLIST applied at the POST /api/queries/preview endpoint. This blacklist filters requests to private and reserved address ranges to prevent authenticated users from pivoting through the server to internal infrastructure. The omission covers RFC 6598 (100.64.0.0/10), the Shared Address Space range originally assigned for CGNAT (Carrier-Grade NAT) but also used by cloud providers and some ISPs for internal routing. In hosting environments where these addresses front internal microservices, metadata APIs, or management interfaces, the missing blacklist entry creates a pathway for SSRF. CWE-918 (Server-Side Request Forgery) describes the root cause: user-controlled URL input causes a server to initiate HTTP requests to unintended destinations, with responses returned to the attacker. CPE cpe:2.3:a:budibase:server:*:*:*:* indicates all known versions are affected.
Know when Budibase gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Builder-role authentication required (PR:L); network endpoint, low complexity; high confidentiality from proxied internal responses; low integrity from potential side-effect requests to internal services.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Budibase backend-core (@budibase/backend-core, as used by @budibase/server) omits the shared address space range 100.64.0.0/10 from its default SSRF blacklist (DEFAULT_BLACKLIST) used by REST datasource query previews. When the default blacklist is active (i.e., a self-hosted deployment has not defined BLACKLIST_IPS), an authenticated user with the Builder permission can submit a REST datasource query preview request to POST /api/queries/preview targeting a reachable HTTP(S) service in the 100.64.0.0/10 range, causing the server to send a request to that target and return its response through the preview flow. Per the advisory, no released fix was identified at the time of publication; remediation is to add 100.64.0.0/10 to DEFAULT_BLACKLIST.
Executive ViewAI
Budibase Server self-hosted deployments contain a Server-Side Request Forgery vulnerability in the REST datasource preview feature that allows authenticated Builder-role users to access internal services on the RFC 6598 shared address space (100.64.0.0/10) and potentially expose confidential data. This vulnerability is limited to self-hosted deployments and requires Builder-level access to exploit. Organizations using self-hosted Budibase should immediately audit Builder role assignments and implement additional network controls.
Implement custom BLACKLIST_IPS configuration to include RFC 6598 range (100.64.0.0/10) and other internal address spaces (RFC 1918, loopback); restrict Builder role to minimal necessary users; deploy network segmentation to prevent Budibase server from accessing internal services; monitor /api/queries/preview endpoint requests for suspicious patterns; implement Web Application Firewall rules to block requests targeting known internal service IPs.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Unauthorized data access in Budibase low-code platform before 3.30.4 allows unauthenticated users to manipulate internal
SQL injection in Budibase's MySQL integration (all versions prior to 3.40.0) lets attackers execute arbitrary, stacked S
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
Remote code execution in Budibase self-hosted server before 3.41.3 lets authenticated administrators run arbitrary JavaS
Account enumeration and targeted denial-of-service in Budibase prior to 3.39.25 stem from an observable response discrep
Unauthenticated account takeover of pending invited users in Budibase Server (@budibase/server) versions 3.41.0 through
EUVD-2026-67693
GHSA-3fqg-454w-h447
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB